Since I saw someone create the URL by hand the other day, I'm going to ask the simple question: is the request hitting the HTTP-POST binding location? POST and Redirect are two different URLs in CAS (and I'm guessing most IdPs).
I've never had to do anything different to handle the two different types of SPs on that version. On Mon, 2021-04-19 at 16:41 +0000, Keith Alston (Staff) wrote: It seems that my CAS SAML2.0 idp is handling SAML2 services that do GET requests just fine. But when I have an SP that does a SAML2 POST request my idp is not reading the parameters and I get the "Application Not Authorized to Use CAS" message instead of the auth page. Difference being parameters in the URI vs parameters in the POST body. Anyone have any idea where I might look to resolve this issue? Are there certain parameters in the service definition that I should be including? Something I'm missing in cas.properties? The audit log does not show POST requests as SAML2_POST though SAML trace does show it as a SAML request. Any clue here would be helpful. TIA! Keith Alston Regent University IT Department [email protected] 757.619.3421 -- - 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/6bad321c10587be379a7cec181afa435c58c8b3e.camel%40ndsu.edu.
