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
The Java clients using Oltu (Feign, Retrofit, Retrofit2) always send the Client ID and Secret in the url-encoded body during the Client Credential flow. This fails for strict OAuth2 server implementations that require it in the HTTP Basic Auth header and reject its appearance in the body.
Agreed. The default should be to use basic auth with an apiclient option to switch to query params (I know some incorrect oauth2 servers that only support the latter)
Description
The Java clients using Oltu (Feign, Retrofit, Retrofit2) always send the Client ID and Secret in the url-encoded body during the Client Credential flow. This fails for strict OAuth2 server implementations that require it in the HTTP Basic Auth header and reject its appearance in the body.
The OAuth2 RFC 6749 - Section 2.3.1 states:
Swagger-codegen version
2.2.1
Suggest a fix/enhancement
The problem lies partially in Oltu, but this line in OAuth.updateAccessToken is where the issue starts:
A workaround is to override
TokenRequestBuilder
:Then change the generated OAuthOkHttpClient to read those headers (as the Oltu URLConnectionClient does )
The text was updated successfully, but these errors were encountered: