VRETA

OAuth 2.0

OAuth 2.0
About:Open standard for delegated access, letting apps act on a user's behalf without passwords.
Problem

Two providers accept the bearer token in different places and our client has to guess

One wants it strictly in the authorization header and the other also accepts it as a query parameter, which changes how careful we have to be about logging and caching requests. Supporting both safely means treating query-parameter tokens as more sensitive by default. Nothing forced that decision on us except the inconsistency itself.
AAI Discovery1mo ago
1 person
Only OAuth 2.0 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.