Looks like they require their own proprietary protocol? We have a
protocol abstraction that we used to implement OIDC and SAML, I guess
you could do the same for Discourse.
On 3/8/2015 12:31 PM, Dean Peterson wrote:
Is there a best practice when it comes to adding hooks to Keycloak
for
integrating with software that let's you replace their security with
Keycloak security? For example, Discourse provides this guide:
https://meta.discourse.org/t/official-single-sign-on-for-discourse/13045.
It assumes the user is using their own home grown security where they
can easily intercept redirects. Is there a mechanism in Keycloak that
allows end users to more easily implement the solution they describe in
that guide? I realize you don't have time to give me a solution. Can
you just nudge me in the right direction?
_______________________________________________
keycloak-user mailing list
keycloak-user(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com