Were you able to find a solution to this? We're running into the same issue with Concur Solutions on CAS v5.2.4.
On Thursday, April 18, 2019 at 3:40:02 PM UTC, JC wrote: > > We are trying to setup CAS 5.2.6 for use with Concur Solutions as the SP. > Per their tech support, they only support IdP initiated SSO and not SP > initiated. I see that the 5.3.x branch of CAS has support for Concur, but I > do not see anything really different in the service record that it creates > in my test environment than the service record I created for 5.2. Just in > case I did move it to our 5.2 test to see if it made a difference, but it > did not. > > I have also played around with using the /cas/idp/Unsolicited/SSO endpoint > in a URL ( > https://cas.example.com/cas/idp/profile/SAML2/Unsolicited/SSO?providerId=https%3A%2F%2Fwww.concursolutions.com&shire=https%3A%2F%2Fwww.concursolutions.com%2FSAMLRedirector%2FClientSAMLLogin.aspx), > > which logs me into CAS and returns the SAML2 callback URL with the > following error > > java.lang.IllegalArgumentException: Requested binding [{}] is not supported > by entity id https://www.concursolutions.com > > > Has anyone gotten this working for Concur? I'm not hugely familiar with > the ins-and-outs of CAS (or SAML), and do not know what binding it is > referring to, or even if CAS is throwing the error or if it is a response > from Concur. Any help would be appreciated. Thanks, > > > James > -- - 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 [email protected]. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/99bfee31-f73f-4124-993e-34f4bfc29f4d%40apereo.org.
