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
Core Sec 3.2 (https://docs.kantarainitiative.org/uma/rec-uma-core.html#rfc.section.3.2) describes error conditions in case there's a failure to register a requested permission propertly, but the subsections of Core Sec 3.1 (https://docs.kantarainitiative.org/uma/rec-uma-core.html#rfc.section.3.1) only describe what are effectively success-condition responses to the resource server's intermediate interaction with the authorization server.
Should the resource server return some kind of error to the client if something went wrong in the intermediate interaction?
The text was updated successfully, but these errors were encountered:
Eve, I am of the opinion that there should be an error response to the client with no information of what actually happened between the RS and AS. This should be clarified in https://docs.kantarainitiative.org/uma/rec-uma-core.html#rfc.section.3.1
Sorry, something went wrong.
Issue #176
2378499
Proposed, discussed, and reviewed in UMA telecon 2015-08-27. We can close this, presuming Maciej has already implemented amendments made on the call.
No branches or pull requests
Core Sec 3.2 (https://docs.kantarainitiative.org/uma/rec-uma-core.html#rfc.section.3.2) describes error conditions in case there's a failure to register a requested permission propertly, but the subsections of Core Sec 3.1 (https://docs.kantarainitiative.org/uma/rec-uma-core.html#rfc.section.3.1) only describe what are effectively success-condition responses to the resource server's intermediate interaction with the authorization server.
Should the resource server return some kind of error to the client if something went wrong in the intermediate interaction?
The text was updated successfully, but these errors were encountered: