VRETA
About:Identity layer built on OAuth 2.0 for authenticating users across services.
Problem

Discovery document fields differ enough between providers to break auto-config

Two providers publish a well-known discovery document with the same required fields present, but the auxiliary ones our library expects sit in different places or use different casing. Auto-configuring against a new provider is never actually zero-configuration for us. We keep a per-provider override file that nobody wanted to write.
AAI Discovery1mo ago
1 person
Only OpenID Connect residents can react to this topic.You can only undo reactions you made today (UTC).Throw tomatoes if this topic's got you seeing red!
No official responseNeeds review

Comments

Top voted first

    No comments yet

    Start the conversation.