I guess "-d client_secret=my_secret" ? ;)
On Wed, Dec 14, 2016 at 8:48 AM, Charles Moulliard <cmoullia(a)redhat.com>
wrote:
How do I provide the client secret within the curl request ? An
example
would be great ;-)
On Wed, Dec 14, 2016 at 8:27 AM, Stian Thorgersen <sthorger(a)redhat.com>
wrote:
> Error message is pretty self explanatory here - you're missing the client
> secret
>
> On 14 December 2016 at 08:17, Charles Moulliard <cmoullia(a)redhat.com>
> wrote:
>
>> Hi,
>>
>> Why do I get this error when I issue tthis curl request to get a token
>>
>> curl -sk -X POST
>>
https://secure-sso-sso.e8ca.engint.openshiftapps.com/auth/re
>> alms/master/protocol/openid-connect/token
>> -d
>> <
https://secure-sso-sso.e8ca.engint.openshiftapps.com/auth/
realms/master/protocol/openid-connect/token-d>
>> grant_type=password -d username=admin -d password=admin -d
>> client_id=demoapp
>>
>> {"error_description":"Client secret not provided in
>> request","error":"unauthorized_client"}
>>
>> Keycloak Version : 1.9.8
>> client_id: demoapp
>>
>> Do I have to set another filed instead of username/password &
>> grant_type=password ?
>>
>> Regards,
>>
>> Charles
>> _______________________________________________
>> keycloak-user mailing list
>> keycloak-user(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/keycloak-user
>>
>
>
_______________________________________________
keycloak-user mailing list
keycloak-user(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user