Mailing-List: contact dev-help@oltu.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@oltu.apache.org
Date: Mon, 14 Sep 2015 09:39:46 +0000 (UTC)
From: "Rikard Swahn (JIRA)" <jira@apache.org>
To: dev@oltu.apache.org
Message-ID: <JIRA.12863369.1441975012000.328524.1442223586749@Atlassian.JIRA>
In-Reply-To: <JIRA.12863369.1441975012000@Atlassian.JIRA>
References: <JIRA.12863369.1441975012000@Atlassian.JIRA>
 <JIRA.12863369.1441975012428@arcas>
Subject: [jira] [Comment Edited] (OLTU-179) Client credentials should only
 be required for the client credentials flow
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Rikard Swahn edited comment on OLTU-179 at 9/14/15 9:39 AM:
------------------------------------------------------------

Well, you have a point, for the Auto code grant it does not really make sense, the spec has to be wrong or very unclear. In the other flows (Resource Owner Password Credentials and refreshing tokens) it is reasonable to not require it I think.


was (Author: rikardswahn):
Well, for the Auto code grant it does not really make sense, the spec has to be wrong or very unclear. In the other flows (Resource Owner Password Credentials and refreshing tokens) it is reasonable to not require it I think.

> Client credentials should only be required for the client credentials flow
> --------------------------------------------------------------------------
>
>                 Key: OLTU-179
>                 URL: https://issues.apache.org/jira/browse/OLTU-179
>             Project: Apache Oltu
>          Issue Type: Bug
>          Components: oauth2-authzserver
>    Affects Versions: oauth2-1.0.0
>            Reporter: Rikard Swahn
>
> Client credentials should not be required for any other flow than the client credentials flow. It is required in Oltu in the "Resource Owner Password Credentials Grant", "Authorization code Grant" (when requesting access token) and when refreshing tokens.
> About refreshing access tokens, taken from http://tools.ietf.org/html/rfc6749#page-47 :
> "If the client type is confidential or
>    the client was issued client credentials (or assigned other
>    authentication requirements), the client MUST authenticate with the
>    authorization server as described in Section 3.2.1."
>    
> About the Resource Owner Password Credentials Grant, taken from http://tools.ietf.org/html/rfc6749#page-37 :
> "If the client type is confidential or the client was issued client
>    credentials (or assigned other authentication requirements), the
>    client MUST authenticate with the authorization server as described
>    in Section 3.2.1.  
> About the "Authorization code Grant" 
> http://tools.ietf.org/html/rfc6749#section-4.1.3 :
>   If the client type is confidential or the client was issued client
>    credentials (or assigned other authentication requirements), the
>    client MUST authenticate with the authorization server as described
>    in Section 3.2.1.
> Note however that for the "Authorization code Grant" the "client_id" param is required if client credentials are not given.
> So the validators for these cases should not set enforceClientAuthentication = true.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)