Secure your Go APIs with Decentralised Identity Tokens
summary
Claims that Go APIs can use did token proofs signed with Ethereum personal_sign and encoded as base64 JSON are demonstrated end to end: a Go API built with Gorilla Mux gets wrapped in a checkBearerToken middleware that calls Magic Admin Go to validate tokens and run getMetadataByToken, returning email, issuer and public address. Demo uses a Next front end template, Postman tests, and a Scrappy Twitter CRUD example; tokens default to 15 minutes (demo shows an 8‑hour option), keys are protected with cloud HSMs, and new accounts get 10,000 free logins.
AI-written summary · about
chapters (19)
- 0:00Securing Go APIs
- 1:14Password auth problems
- 3:00Zero knowledge & blockchain keys
- 4:02Magic improves DID tokens
- 5:25What is a DID token
- 7:10Generating DID tokens with Magic SDK
- 8:54Auth vs authorization
- 9:58Magic link login flow
- 12:04Basic Go API setup
- 14:12Protecting Go API routes with DID
- 18:48Validating DID tokens in Go
- 20:16Frontend DID token integration
- 21:42Testing routes with Postman
- 24:33Next steps & Magic setup
- 25:57Go REST API demo with Magic
- 28:46Resources and documentation links
- 30:10Recap & local setup
- 31:56More DID token resources
- 32:39Q&A
related talks
42mSecuring PHP APIs with Decentralised Identity Tokens
30mA Token Of Respect: Implementing Microservice Identity And Access Management In Go
30mSecuring Your Services with Authentication, Authorization, and RBAC in gRPC
39mSecure your APIs using OAuth2 and OpenID Connect
18mSecure your Apps and APIs with strong authentication and Adaptive Access.
34mAuthenticating your single page apps using JSON Web Tokens
27mAuthentication for the REST of us
32mPortable Sessions with JSON Web Tokens