The proxy can only do openid connect. There are a number of saml proxies
out there already for Apache HTTPD.
On 3/19/2015 2:00 AM, Lohitha Chiranjeewa wrote:
Hi,
I have been trying to use the KeyCloak proxy to authorize my client
application.
In the application configurations, I have the option of setting the
'Client Protocol' to be either 'Saml' or 'OpenId-connect'.
Although I
have set it to both the options in my tests, I received the same
response. It included 17 headers, which had KEYCLOAK_ACCESS_TOKEN,
KEYCLOAK_SUBJECT, KEYCLOAK_USERNAME among others. No other useful
information were included.
My question is, what is the difference I am supposed to expect in the
responses between Saml and OpenId-Connect protocols? If I get a valid
Saml response (XML), where is it exactly located?
Thanks!
_______________________________________________
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