The most scalable and customizable identity server on the market. Replace your Homegrown, Auth0, Okta, Firebase with better UX and DX. Has all the tablestakes: Passkeys, Social Sign In, Multi-Factor Auth, SMS, SAML, TOTP, and more. Written in Go, cloud native, headless, API-first. Available as a service on Ory Network and for self-hosters.
Once a user identifies via Kratos, there could be a need to get further information from Discord using the returned token (similar to how Kratos's Discord provider does this internally). In order to do this, at the very least the returned AccessToken would need to be able to be able to be accessed.
Describe your ideal solution
The ideal solution would be to repurpose some parts of the claim to include the access and refresh tokens.
Workarounds or alternatives
Not use Kratos and implement my own oAuth. Without this info being able to be stored somewhere the info seems to be impossible to get.
Preflight checklist
Describe your problem
Once a user identifies via Kratos, there could be a need to get further information from Discord using the returned token (similar to how Kratos's Discord provider does this internally). In order to do this, at the very least the returned AccessToken would need to be able to be able to be accessed.
Describe your ideal solution
The ideal solution would be to repurpose some parts of the claim to include the access and refresh tokens.
Workarounds or alternatives
Not use Kratos and implement my own oAuth. Without this info being able to be stored somewhere the info seems to be impossible to get.
Version
0.10.1
Additional Context
https://discord.com/developers/docs/topics/oauth2#shared-resources-oauth2-scopes in case somebody needs a link