oltu-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stein Welberg (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBER-49) AuthorizationCodeValidator needs to be updated to latest spec
Date Tue, 16 Oct 2012 07:53:03 GMT

    [ https://issues.apache.org/jira/browse/AMBER-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13476831#comment-13476831
] 

Stein Welberg commented on AMBER-49:
------------------------------------

Another thing we might add to the validators is the fact whether to accept the client_id and
client_secret as form parameters or not. The spec states that an authorization server might
reject this, see [0].

I have time to implement this validation :-).

[0] http://tools.ietf.org/html/rfc6749#section-2.3.1
                
> AuthorizationCodeValidator needs to be updated to latest spec
> -------------------------------------------------------------
>
>                 Key: AMBER-49
>                 URL: https://issues.apache.org/jira/browse/AMBER-49
>             Project: Amber
>          Issue Type: Bug
>          Components: OAuth 2.0 - Authorization Server
>            Reporter: Antonio Sanso
>            Assignee: Antonio Sanso
>         Attachments: use-client-auth-header.patch
>
>
> The authorization code grant type it wrongly automatically validates that the client
ID and secret are there.
> See also [0]
> [0] http://amber.markmail.org/message/b7q5lpe2ijh7lfrv

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message