Skip to content
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.

Sign up for GitHub

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

Jump to bottom

OIDC: Always lookup client well-known during server selection #25472

Closed
Tracked by #25392
kerryarchibald opened this issue May 30, 2023 · 0 comments
Closed
Tracked by #25392

OIDC: Always lookup client well-known during server selection #25472

kerryarchibald opened this issue May 30, 2023 · 0 comments
Assignees
@kerryarchibald
Labels
A-Authentication A-OIDC T-Enhancement Z-Labs

Comments

@kerryarchibald
Copy link
Contributor

kerryarchibald commented May 30, 2023 •
edited
Loading

Homeserver .well-known is to be used to determine OIDC support
We sometimes fetch the well-known during server selection or login -

  1. When a server without a protocol is entered ('matrix.org')
  2. When a username with an @ sign is entered

AC:

  • .well-known is fetched for default and custom servers during server selection
  • The validated server config used in Registration and Login uses the validated result from the well-known when it exists
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kerryarchibald kerryarchibald

Labels
A-Authentication A-OIDC T-Enhancement Z-Labs
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@kerryarchibald