You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oltu.apache.org by "Samuel Sayer (Created) (JIRA)" <ji...@apache.org> on 2011/11/07 19:48:52 UTC
[jira] [Created] (AMBER-43) Missing OAuth parameter is ambiguous
for a resource request
Missing OAuth parameter is ambiguous for a resource request
-----------------------------------------------------------
Key: AMBER-43
URL: https://issues.apache.org/jira/browse/AMBER-43
Project: Amber
Issue Type: Improvement
Components: OAuth 2.0 - Resource Server
Reporter: Samuel Sayer
Priority: Minor
When required attributes are missing from an OAuthAccessResourceRequest, an exception is thrown with a generic message "OAuth parameters were not found". Debugging is much easier if the underlying reason (missing token, missing header) is included with the exception being thrown.
--
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-43) Missing OAuth parameter is ambiguous
for a resource request
Posted by "Samuel Sayer (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMBER-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Samuel Sayer updated AMBER-43:
------------------------------
Attachment: patchfile
Patchfile for the issue
> Missing OAuth parameter is ambiguous for a resource request
> -----------------------------------------------------------
>
> Key: AMBER-43
> URL: https://issues.apache.org/jira/browse/AMBER-43
> Project: Amber
> Issue Type: Improvement
> Components: OAuth 2.0 - Resource Server
> Reporter: Samuel Sayer
> Priority: Minor
> Labels: patch
> Attachments: patchfile
>
>
> When required attributes are missing from an OAuthAccessResourceRequest, an exception is thrown with a generic message "OAuth parameters were not found". Debugging is much easier if the underlying reason (missing token, missing header) is included with the exception being thrown.
--
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] [Resolved] (AMBER-43) Missing OAuth parameter is ambiguous
for a resource request
Posted by "Lukasz Moren (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMBER-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lukasz Moren resolved AMBER-43.
-------------------------------
Resolution: Fixed
Thanks, patch applied
> Missing OAuth parameter is ambiguous for a resource request
> -----------------------------------------------------------
>
> Key: AMBER-43
> URL: https://issues.apache.org/jira/browse/AMBER-43
> Project: Amber
> Issue Type: Improvement
> Components: OAuth 2.0 - Resource Server
> Reporter: Samuel Sayer
> Priority: Minor
> Labels: patch
> Attachments: patchfile
>
>
> When required attributes are missing from an OAuthAccessResourceRequest, an exception is thrown with a generic message "OAuth parameters were not found". Debugging is much easier if the underlying reason (missing token, missing header) is included with the exception being thrown.
--
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-43) Missing OAuth parameter is ambiguous
for a resource request
Posted by "Tommaso Teofili (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMBER-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tommaso Teofili updated AMBER-43:
---------------------------------
Fix Version/s: 0.22
> Missing OAuth parameter is ambiguous for a resource request
> -----------------------------------------------------------
>
> Key: AMBER-43
> URL: https://issues.apache.org/jira/browse/AMBER-43
> Project: Amber
> Issue Type: Improvement
> Components: OAuth 2.0 - Resource Server
> Reporter: Samuel Sayer
> Priority: Minor
> Labels: patch
> Fix For: 0.22
>
> Attachments: patchfile
>
>
> When required attributes are missing from an OAuthAccessResourceRequest, an exception is thrown with a generic message "OAuth parameters were not found". Debugging is much easier if the underlying reason (missing token, missing header) is included with the exception being thrown.
--
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-43) Missing OAuth parameter is ambiguous for
a resource request
Posted by "Antonio Sanso (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMBER-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Antonio Sanso closed AMBER-43.
------------------------------
> Missing OAuth parameter is ambiguous for a resource request
> -----------------------------------------------------------
>
> Key: AMBER-43
> URL: https://issues.apache.org/jira/browse/AMBER-43
> Project: Amber
> Issue Type: Improvement
> Components: OAuth 2.0 - Resource Server
> Reporter: Samuel Sayer
> Priority: Minor
> Labels: patch
> Fix For: 0.22
>
> Attachments: patchfile
>
>
> When required attributes are missing from an OAuthAccessResourceRequest, an exception is thrown with a generic message "OAuth parameters were not found". Debugging is much easier if the underlying reason (missing token, missing header) is included with the exception being thrown.
--
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