[keycloak-user] Alternative to Kerberos & Custom Use Case

[Leandro Del Sole]

I think what you're looking for is:
https://www.keycloak.org/docs/latest/securing_apps/index.html#external-token-to-internal-token-exchange

Probably this specific part:
https://www.keycloak.org/docs/latest/securing_apps/index.html#external-token-to-internal-token-exchange

It's worth reading all the possibilites to see which fit betters for your
case.

I'm glad to hear if there are better options to achieve this, I have a
similar scenario here.

Em ter, 6 de ago de 2019 às 20:48, Aditya Bhole <Aditya.Bhole at veritas.com>
escreveu:

> Hi,
>
> Are there any other mechanisms in Keycloak apart from Kerberos which can
> establish something similar to a cross realm trust?
>
> Also, consider this use case: We have App A and App B. App A and App B may
> have different Keycloak instances or maybe in different realms of the same
> Keycloak instance. User logs into App A. He clicks on a button in App A
> which is supposed to take him to App B. The user now has a JWT when he
> logged into App A. Now App B knows that all the redirects are going to be
> from App A. So can App B verify the token through App A?
>
> Regards,
> Aditya
> _______________________________________________
> keycloak-user mailing list
> keycloak-user at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/keycloak-user
>