Skip to content

Satosa OIDC Frontend without Database? #403

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
shaardie opened this issue Jun 30, 2022 · 1 comment
Closed

Satosa OIDC Frontend without Database? #403

shaardie opened this issue Jun 30, 2022 · 1 comment

Comments

@shaardie
Copy link
Contributor

This is a more of a question than an issue. I would have used the mailing list, but unfortunately the link to it is broken.

I saw some commit about stateless workflows for the OIDC Frontend, does that mean that there is no need for a database anymore for this use case?

According to the docs they are still required.

@c00kiemon5ter
Copy link
Member

There has been some work on pyop to allow the frontend to work without a database. The way this works is by turning the tokens into JWTs and storing all the needed data within it.

While this approach works for certain use-cases, it has its own drawbacks. Most importantly, there is no way to revoke a token; the only mitigation is to change the signing key thus rendering all tokens invalid. This forces you to keep the access_token active for a short period of time.

PS: sorry about the link, I will look into fixing it asap

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants