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
M_AUTHENTICATION
Current code here relies on client well-known Use OidcClientStore instead, which falls back to authenticated issuer.
OidcClientStore
No response
No
The text was updated successfully, but these errors were encountered:
Fix after #25394
Sorry, something went wrong.
I'm unsure how to triage this since I don't know what 'OP' refers to, and since there's a fix that's ready to merge, I'll leave it untriaged
kerryarchibald
Successfully merging a pull request may close this issue.
Steps to reproduce
M_AUTHENTICATION
to config.json, using a homeserver that does not have a client/well-knownOutcome
What did you expect?
What happened instead?
Current code here relies on client well-known
Use
OidcClientStore
instead, which falls back to authenticated issuer.Operating system
No response
Browser information
No response
URL for webapp
No response
Application version
No response
Homeserver
No response
Will you send logs?
No
The text was updated successfully, but these errors were encountered: