You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oltu.apache.org by "Ed Anuff (JIRA)" <ji...@apache.org> on 2011/09/16 05:42:08 UTC

[jira] [Created] (AMBER-29) OAUTH_HEADER_NAME needs to be updated to latest spec

OAUTH_HEADER_NAME needs to be updated to latest spec
----------------------------------------------------

                 Key: AMBER-29
                 URL: https://issues.apache.org/jira/browse/AMBER-29
             Project: Amber
          Issue Type: Bug
          Components: OAuth 2.0 - Authorization Server, OAuth 2.0 - Resource Server, Parent
    Affects Versions: 1.0
            Reporter: Ed Anuff


org.apache.amber.oauth2.common.OAuth.OAUTH_HEADER_NAME is set to "OAuth", is should be set to "Bearer"

http://tools.ietf.org/html/draft-ietf-oauth-v2-bearer-08#section-2.4

There probably should be a meta-issue or something to make sure everything in org.apache.amber.oauth2.common.OAuth is updated to the latest version of the spec, since thats the same problem as with AMBER-28

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Resolved] (AMBER-29) OAUTH_HEADER_NAME needs to be updated to latest spec

Posted by "Lukasz Moren (Resolved) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AMBER-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lukasz Moren resolved AMBER-29.
-------------------------------

    Resolution: Fixed
    
> OAUTH_HEADER_NAME needs to be updated to latest spec
> ----------------------------------------------------
>
>                 Key: AMBER-29
>                 URL: https://issues.apache.org/jira/browse/AMBER-29
>             Project: Amber
>          Issue Type: Bug
>          Components: OAuth 2.0 - Authorization Server, OAuth 2.0 - Resource Server, Parent
>    Affects Versions: 1.0
>            Reporter: Ed Anuff
>            Assignee: Antonio Sanso
>         Attachments: OAuth.java.diff, OAuthUtils.java.diff
>
>
> org.apache.amber.oauth2.common.OAuth.OAUTH_HEADER_NAME is set to "OAuth", is should be set to "Bearer"
> http://tools.ietf.org/html/draft-ietf-oauth-v2-bearer-08#section-2.4
> There probably should be a meta-issue or something to make sure everything in org.apache.amber.oauth2.common.OAuth is updated to the latest version of the spec, since thats the same problem as with AMBER-28

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (AMBER-29) OAUTH_HEADER_NAME needs to be updated to latest spec

Posted by "Antonio Sanso (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AMBER-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13201187#comment-13201187 ] 

Antonio Sanso commented on AMBER-29:
------------------------------------

Hi Ed thanks,

the patch is fine from the spec point of view but it'd be good if you could also align the tests. 

Results :

Failed tests:   testEncodeOAuthHeader(org.apache.amber.oauth2.common.OAuthUtilsTest): expected:<[OAuth] error="invalid_toke...> but was:<[Bearer] error="invalid_toke...>

                
> OAUTH_HEADER_NAME needs to be updated to latest spec
> ----------------------------------------------------
>
>                 Key: AMBER-29
>                 URL: https://issues.apache.org/jira/browse/AMBER-29
>             Project: Amber
>          Issue Type: Bug
>          Components: OAuth 2.0 - Authorization Server, OAuth 2.0 - Resource Server, Parent
>    Affects Versions: 1.0
>            Reporter: Ed Anuff
>            Assignee: Antonio Sanso
>         Attachments: OAuth.java.diff, OAuthUtils.java.diff
>
>
> org.apache.amber.oauth2.common.OAuth.OAUTH_HEADER_NAME is set to "OAuth", is should be set to "Bearer"
> http://tools.ietf.org/html/draft-ietf-oauth-v2-bearer-08#section-2.4
> There probably should be a meta-issue or something to make sure everything in org.apache.amber.oauth2.common.OAuth is updated to the latest version of the spec, since thats the same problem as with AMBER-28

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (AMBER-29) OAUTH_HEADER_NAME needs to be updated to latest spec

Posted by "Ed Anuff (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AMBER-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ed Anuff updated AMBER-29:
--------------------------

    Attachment: OAuthUtils.java.diff
                OAuth.java.diff

update header names
                
> OAUTH_HEADER_NAME needs to be updated to latest spec
> ----------------------------------------------------
>
>                 Key: AMBER-29
>                 URL: https://issues.apache.org/jira/browse/AMBER-29
>             Project: Amber
>          Issue Type: Bug
>          Components: OAuth 2.0 - Authorization Server, OAuth 2.0 - Resource Server, Parent
>    Affects Versions: 1.0
>            Reporter: Ed Anuff
>         Attachments: OAuth.java.diff, OAuthUtils.java.diff
>
>
> org.apache.amber.oauth2.common.OAuth.OAUTH_HEADER_NAME is set to "OAuth", is should be set to "Bearer"
> http://tools.ietf.org/html/draft-ietf-oauth-v2-bearer-08#section-2.4
> There probably should be a meta-issue or something to make sure everything in org.apache.amber.oauth2.common.OAuth is updated to the latest version of the spec, since thats the same problem as with AMBER-28

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Assigned] (AMBER-29) OAUTH_HEADER_NAME needs to be updated to latest spec

Posted by "Antonio Sanso (Assigned) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AMBER-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Antonio Sanso reassigned AMBER-29:
----------------------------------

    Assignee: Antonio Sanso
    
> OAUTH_HEADER_NAME needs to be updated to latest spec
> ----------------------------------------------------
>
>                 Key: AMBER-29
>                 URL: https://issues.apache.org/jira/browse/AMBER-29
>             Project: Amber
>          Issue Type: Bug
>          Components: OAuth 2.0 - Authorization Server, OAuth 2.0 - Resource Server, Parent
>    Affects Versions: 1.0
>            Reporter: Ed Anuff
>            Assignee: Antonio Sanso
>         Attachments: OAuth.java.diff, OAuthUtils.java.diff
>
>
> org.apache.amber.oauth2.common.OAuth.OAUTH_HEADER_NAME is set to "OAuth", is should be set to "Bearer"
> http://tools.ietf.org/html/draft-ietf-oauth-v2-bearer-08#section-2.4
> There probably should be a meta-issue or something to make sure everything in org.apache.amber.oauth2.common.OAuth is updated to the latest version of the spec, since thats the same problem as with AMBER-28

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (AMBER-29) OAUTH_HEADER_NAME needs to be updated to latest spec

Posted by "Tommaso Teofili (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AMBER-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tommaso Teofili updated AMBER-29:
---------------------------------

    Fix Version/s: 0.22
    
> OAUTH_HEADER_NAME needs to be updated to latest spec
> ----------------------------------------------------
>
>                 Key: AMBER-29
>                 URL: https://issues.apache.org/jira/browse/AMBER-29
>             Project: Amber
>          Issue Type: Bug
>          Components: OAuth 2.0 - Authorization Server, OAuth 2.0 - Resource Server, Parent
>    Affects Versions: 1.0
>            Reporter: Ed Anuff
>            Assignee: Antonio Sanso
>             Fix For: 0.22
>
>         Attachments: OAuth.java.diff, OAuthUtils.java.diff
>
>
> org.apache.amber.oauth2.common.OAuth.OAUTH_HEADER_NAME is set to "OAuth", is should be set to "Bearer"
> http://tools.ietf.org/html/draft-ietf-oauth-v2-bearer-08#section-2.4
> There probably should be a meta-issue or something to make sure everything in org.apache.amber.oauth2.common.OAuth is updated to the latest version of the spec, since thats the same problem as with AMBER-28

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (AMBER-29) OAUTH_HEADER_NAME needs to be updated to latest spec

Posted by "sharmila r (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AMBER-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13157002#comment-13157002 ] 

sharmila r commented on AMBER-29:
---------------------------------

Any updates on this?
                
> OAUTH_HEADER_NAME needs to be updated to latest spec
> ----------------------------------------------------
>
>                 Key: AMBER-29
>                 URL: https://issues.apache.org/jira/browse/AMBER-29
>             Project: Amber
>          Issue Type: Bug
>          Components: OAuth 2.0 - Authorization Server, OAuth 2.0 - Resource Server, Parent
>    Affects Versions: 1.0
>            Reporter: Ed Anuff
>
> org.apache.amber.oauth2.common.OAuth.OAUTH_HEADER_NAME is set to "OAuth", is should be set to "Bearer"
> http://tools.ietf.org/html/draft-ietf-oauth-v2-bearer-08#section-2.4
> There probably should be a meta-issue or something to make sure everything in org.apache.amber.oauth2.common.OAuth is updated to the latest version of the spec, since thats the same problem as with AMBER-28

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Closed] (AMBER-29) OAUTH_HEADER_NAME needs to be updated to latest spec

Posted by "Antonio Sanso (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AMBER-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Antonio Sanso closed AMBER-29.
------------------------------

    
> OAUTH_HEADER_NAME needs to be updated to latest spec
> ----------------------------------------------------
>
>                 Key: AMBER-29
>                 URL: https://issues.apache.org/jira/browse/AMBER-29
>             Project: Amber
>          Issue Type: Bug
>          Components: OAuth 2.0 - Authorization Server, OAuth 2.0 - Resource Server, Parent
>    Affects Versions: 1.0
>            Reporter: Ed Anuff
>            Assignee: Antonio Sanso
>             Fix For: 0.22
>
>         Attachments: OAuth.java.diff, OAuthUtils.java.diff
>
>
> org.apache.amber.oauth2.common.OAuth.OAUTH_HEADER_NAME is set to "OAuth", is should be set to "Bearer"
> http://tools.ietf.org/html/draft-ietf-oauth-v2-bearer-08#section-2.4
> There probably should be a meta-issue or something to make sure everything in org.apache.amber.oauth2.common.OAuth is updated to the latest version of the spec, since thats the same problem as with AMBER-28

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira