2 ms·
You'd have FusionAuth issue the tokens through an authentication event (typically the authorization code grant for interactive sessions). Lots of flows with seq
by mooreds 3y ago
You'd have FusionAuth issue the tokens through an authentication event (typically the authorization code grant for interactive sessions). Lots of flows with sequence diagrams outlined here [0].
Then store the tokens on the client. For browsers dealing with first party apps (everything under the same domain) we recommend cookie storage of these tokens [1].
Then have Caddy examine the tokens provided by the browser. Here's an example Caddy config I put together for a workshop [2].
Finally, depending on your security posture, you might want to verify tokens both in app and at the proxy.
0: https://fusionauth.io/articles/login-authentication-workflows/ https://fusionauth.io/articles/login-authentication-workflow...
1: https://fusionauth.io/articles/oauth/oauth-token-storage https://fusionauth.io/articles/oauth/oauth-token-storage
2: https://github.com/FusionAuth/fusionauth-example-php-api-workshop/blob/main/gateway/caddy.json https://github.com/FusionAuth/fusionauth-example-php-api-wor...