RHi @Antoni! Thanks for reaching out & providing this context - I'm going to look into this now and provide you with an answer as soon as possible!
RCould you give me a bit of insight as to why you're attempting to completely avoid redirection in this case? Are you concerned about potential user churn/drop off during the flow? @Antoni
S@peintnermax maybe has some more input here
As I see it, this is the exact same flow we use in our typescript login to register under https://github.com/zitadel/typescript/tree/main/apps/login#register.
The result is that you have a freshly created user, which is already authenticated and you can use the OIDC token for further calls.
Do I correctly understand the need here?
As I see it, this is the exact same flow we use in our typescript login to register under https://github.com/zitadel/typescript/tree/main/apps/login#register.
The result is that you have a freshly created user, which is already authenticated and you can use the OIDC token for further calls.
Do I correctly understand the need here?
GitHub
Typescript packages and application to showcase the ZITADEL resource API - zitadel/typescript
R@Antoni - Just making sure you were able to see this! Let me know if this aligns with what you're looking for
RNo problem! Please let us know if there's anything else we can do to help!
FThe thing with the oidc flow is, that per definition the standard is always with a redirect. Only option for you at the moment is to use the session api and therefore a session token. which we know is not a oidc token, as it is not created through the standards flow.
FThere is an open issues to implement a token exchange so you can exchange a session token for a oidc token. unfortunately this is not yet implemented: https://github.com/zitadel/zitadel/issues/7900
GitHub
We should allow Session Tokens to be exchanged for OAuth / OIDC tokens on the Token Exchange. This would give developers the opportunity to get an access_token from a session token, without the nee...
FI think the main limitation is, it is not based on a standard, therefore if you want to integrate an app with oidc that will not work. the token itself is opaque so you will have to get the session and implement what you want to check. Generally i think this guide is a helpful starting point: https://docs-git-scalar-zitadel.vercel.app/docs/guides/integrate/login-ui/session-validation#token-introspection
Sessions represent the state of a user session in ZITADEL. They can be aggregated and updated over time to reflect
