So lets see if I can keep this simple.

I have a mostly working CAS 5.3.3 Server with SAML 1.1 working to the 
java-cas-client.  We have a vendor developed CAS Client for the CAS SAML 
1.1 protocol, that worked with CAS 3.3, 3.5, and 3.6.  Now on CAS 5.3.3, 
it's getting a samllp:RequestDenied samllp:Response.

Based on reviewing the code, it appears it's failing at 
Do i need to create a SamlRegisteredService service definition for SAML 1.1 
instead of using RegexRegisteredService?  Based on the error, I expected to 
see service as part of the validation request to /samlValidate, but it's 
not part of the SAML 1.1 specification that I can find.

The received response:
<?xml version="1.0" encoding="UTF-8"?>
            IssueInstant="2018-09-10T15:36:21.756Z" MajorVersion="1"
                <saml1p:StatusCode Value="saml1p:RequestDenied"/>
                <saml1p:StatusMessage>Ticket 'ST-104183-xxxxxxxxxxxxx-cas' 
does not match supplied service. The original service was 
'' and the supplied service was 

- Website:
- Gitter Chatroom:
- List Guidelines:
- Contributions:
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 view this discussion on the web visit

Reply via email to