You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"If the client instance calls an RS without an access token, or with an invalid access token, the RS MAY respond to the client instance with an authentication header indicating that GNAP needs to be used to access the resource".
This response is adequate only when a single AS is being considered. However, the response should be able to support the context of more than one AS and should allow the client to likely succeed in its next attempt.
The protocol should also allow the end-user to indicate his consent whereas this is not the case presently when using an opaque handle.
The response should be able to include the same parameters as those described under the Issue "Tentative proposal for a RS discovery mechanism" #190.
The text was updated successfully, but these errors were encountered:
In section 9.4, the text states:
"If the client instance calls an RS without an access token, or with an invalid access token, the RS MAY respond to the client instance with an authentication header indicating that GNAP needs to be used to access the resource".
This response is adequate only when a single AS is being considered. However, the response should be able to support the context of more than one AS and should allow the client to likely succeed in its next attempt.
The protocol should also allow the end-user to indicate his consent whereas this is not the case presently when using an opaque handle.
The response should be able to include the same parameters as those described under the Issue "Tentative proposal for a RS discovery mechanism" #190.
The text was updated successfully, but these errors were encountered: