Morning, My suggestion is to treat cas 6 as a product replacement rather than an upgrade. Cas 6 uses the gradle build, and it looks like it is ignoring your configuration. The page you see is the default success page.
Ray On Mon, 2021-02-08 at 11:16 -0800, Morning Star wrote: Notice: This message was sent from outside the University of Victoria email system. Please be cautious with links and sensitive information. Hi Team, We are working on upgrading CAS from 3.5.2 to 6.2.2. Additional Info : Spring Boot - 2.2.8, ldaptive – 2.0.1, Lombok – 1.18.12, Server – Tomcat 9. We followed the steps from https://apereo.github.io/cas/6.2.x/protocol/SAML-Protocol.html Added Saml dependency and repository: <dependency> <groupId>org.apereo.cas</groupId> <artifactId>cas-server-support-saml</artifactId> <version>${cas.version}</version> <scope>provided</scope> </dependency> <repositories> <repository> <id>shibboleth-releases</id> <url>https://build.shibboleth.net/nexus/content/repositories/releases</url> </repository> </repositories> >From our application, we are trying to open document via other app from same >domain: On click of “Download Application”, we are getting CAS default login successful page with below URL. https://domain.com/cas/login?TARGET=https%3A%2F%2Fdomain.com%2Fabc%2Fxyz%3Fid%3Dg241079e3nyyyyy6b90fcng7fcb156595549%26source%3DEF%26dName%3DAnu%2520Gopal%2520Test%26dContext%3DD Before Upgrade : We got 302 status code along with SAMLart as a query parameter from CAS server. After Upgrade : We are getting 200 status code and landed on below page. [cas.png] cas.properties : cas.server.name=http://localhost:8080 cas.server.prefix=${cas.server.name}/cas cas.securityContext.casProcessingFilterEntryPoint.loginUrl=${cas.server.prefix}/login cas.securityContext.ticketValidator.casServerUrlPrefix=${cas.server.prefix} cas.securityContext.status.allowedSubnet=127.0.0.1 Service Registry JSON file : { "@class" : "org.apereo.cas.services.RegexRegisteredService", "serviceId" : "^(https?|imaps?)://(([A-Za-z0-9_-]+.)*example.com/.*|example2.com:8090/.*)", "name" : "web", "description" : "Allows HTTP(S) and IMAP(S) protocols", "id" : 10000001, "evaluationOrder" : 1, "usernameAttribute" : "email", "allowedAttributes" : ["CN", "uid", "email"], } Whether samlvalidation is happening in our application? Configuration wise are we missing anything during CAS authentication? Please provide the checklist/document to enable saml 1.1 protocal in CAS. Please help in resolving the issue. -- Ray Bon Programmer Analyst Development Services, University Systems 2507218831 | CLE 019 | [email protected]<mailto:[email protected]> I respectfully acknowledge that my place of work is located within the ancestral, traditional and unceded territory of the Songhees, Esquimalt and WSÁNEĆ Nations. -- - 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/1da1e14edeb69cabe4d20c263b6d7bf87f72cca6.camel%40uvic.ca.
