We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Refactor auth component to use the new OIDC.
Also we might try to use the same JWT for the backend as we use for the frontend so we don't have to log in after a restart...
The text was updated successfully, but these errors were encountered:
KIR-465 Use the new OIDC for getting profile
Sorry, something went wrong.
After the cookie update on the frontend #781 The admin panel should work with the same jwt cookie too, authenticated api calls work from the browser
No, I mean to use JWT instead of JSESSIONID for the backend.
Yeah, me too. I started doing it here: #786
No branches or pull requests
Refactor auth component to use the new OIDC.
Also we might try to use the same JWT for the backend as we use for the frontend so we don't have to log in after a restart...
The text was updated successfully, but these errors were encountered: