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.

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

If the resource server is unsuccessful in registering a permission, how does it respond to the client? #176

Closed
xmlgrrl opened this issue Jul 20, 2015 · 2 comments

Comments

Projects
None yet
2 participants
@xmlgrrl
Copy link

commented Jul 20, 2015

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?

@xmlgrrl xmlgrrl added the core label Jul 20, 2015

@mmachulak

This comment has been minimized.

Copy link

commented Jul 20, 2015

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

@xmlgrrl xmlgrrl added the blocking label Jul 30, 2015

@xmlgrrl xmlgrrl added this to the V1.0.1 milestone Jul 31, 2015

@xmlgrrl xmlgrrl added the V1.0.1 label Aug 13, 2015

mmachulak added a commit that referenced this issue Aug 27, 2015

@xmlgrrl

This comment has been minimized.

Copy link
Author

commented Aug 28, 2015

Proposed, discussed, and reviewed in UMA telecon 2015-08-27. We can close this, presuming Maciej has already implemented amendments made on the call.

@xmlgrrl xmlgrrl closed this Aug 28, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.