I'm just wondering if anyone figured this out. I have the same issue--SAML Responses from CAS are NOT base64 encoded, but all the clients I have seem to expect the SAML Response to be base64 encoded.
Is this a SAML spec, that it should be base64 encoded and CAS isn't implementing it properly? On Wednesday, September 18, 2019 at 4:55:58 PM UTC-4, Chris H wrote: > > > I am working with client who's running a CAS server (a backpatched > version of 3.4.12) as their IdP. We are trying to connect this with our > product, a SAML SP implemented with OneLogin's PHP client. > > The issue we are having is that the "SAMLResponse" POST parameter is > coming over in raw form, ie it is not base64 encoded. The OneLogin lib > appears to assume that this value is base64 encoded and throws an exception > when it is not. I do not see any configuration to override this behaviour. > > Is it possible to configure CAS to base64 encode this value before > sending? > > Any idea why this would be happening? We have several active SAML2 > integrations with other clients who use CAS as their IdP. > > Thanks! > Chris > -- - Website: https://apereo.github.io/cas - Gitter Chatroom: https://gitter.im/apereo/cas - List Guidelines: https://goo.gl/1VRrw7 - Contributions: https://goo.gl/mh7qDG --- You received this message because you are subscribed to the Google Groups "CAS Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to cas-user+unsubscr...@apereo.org. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/464a638f-6566-474b-b2d3-74202141986d%40apereo.org.
