Hey Vlasta,
thanks for your reply. I tried recreating the IDP from scratch but it
resulted in the same error. Wondering if there is any change in the
behaviour between Keycloak 3 and 4 that could cause this? I noticed that
Keacloak 4 has a lot more settings, but unsure which one could trigger the
oauth token request to fail.
Regards,
Peter
On Thu, Mar 28, 2019 at 10:33 AM Vlasta Ramik <vramik(a)redhat.com> wrote:
Hey Peter,
I'd start at
https://www.keycloak.org/docs/latest/server_admin/index.html#github and
try to create the idp from scratch and see if it works or not and why.
Regards,
V.
On 3/27/19 11:17 AM, Peter Braun wrote:
> Hey everyone,
>
> i'm having trouble with the Github Identity Provider in Keycloak 4 (using
> RH-SSO 7.3) where it was working fine with Keycloak 3 (RH-SSO 7.2).
Realm,
> Client and Provider are configured in the same way but login fails and I
> get this error in the logs:
>
> *09:14:19,823 ERROR
> [org.keycloak.broker.oidc.AbstractOAuth2IdentityProvider] (default
task-71)
> Failed to make identity provider oauth callback:
> org.keycloak.broker.provider.IdentityBrokerException: No access token
> available in OAuth server response:
>
{"error":"unauthorized_client","error_description":"The
client is not
> authorized to request a token using this method."}*
>
> I've already checked that the credentials are correct and that the realm,
> client and idp settings are similar to the Keycloak 3 instance. Any Idea
> where to best start looking?
>
>
> Regards,
> Peter
> _______________________________________________
> keycloak-user mailing list
> keycloak-user(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/keycloak-user