fiber-server

Fiber Server Example

Schnallbert says: "Fiber fast, auth tight — let's go!"

A minimal Fiber HTTP server demonstrating goAuthly authentication middleware.

What it demonstrates

• JWT verification — Bearer tokens validated against a local JWKS endpoint.
• Opaque token verification — Bearer tokens introspected via a local RFC 7662 endpoint.
• Basic Auth — Username/password verified with bcrypt.
• Required metadata — The X-User-Sub header must be present on protected routes.

How to run

cd examples/fiber-server
go run .

The server starts on :8081 and prints example tokens to the console:

=== Example Tokens ===
JWT: eyJhbGciOi...
Opaque: opaque-good

Routes

Testing with curl

Replace <JWT> with the token printed at startup.

Public endpoint (no auth)

curl http://localhost:8081/public

Protected endpoint with JWT

curl -H "Authorization: Bearer <JWT>" \
     -H "X-User-Sub: demo-user" \
     http://localhost:8081/protected

Protected endpoint with opaque token

curl -H "Authorization: Bearer opaque-good" \
     -H "X-User-Sub: demo-user" \
     http://localhost:8081/protected

Basic auth endpoint

curl -u demo:password \
     http://localhost:8081/basic

Expected failure (missing X-User-Sub)

curl -H "Authorization: Bearer <JWT>" \
     http://localhost:8081/protected
# Returns 401

Notes

• RSA keys are generated at startup — tokens are only valid for the current process.
• Credentials (demo / password) are for demonstration only. Never use them in production.
• A mock JWKS and introspection server runs on 127.0.0.1:9090 alongside the Fiber app.