New install of Cas 6.1.0, json service not working

[Pablo Vidaurri]

I added below dependency:

   compile "org.apereo.cas:cas-server-support-json-service-registry:${project.'cas.version'}"

I'm testing on windows at the moment and added the following to cas.properties in d:/etc/cas/config

cas.serviceRegistry.json.location: file:D:/etc/cas/services

cas.serviceRegistry.initFromJson: true

I have following wildcard service Id in D:/etc/cas/services/localhost-2019030300010.json:

{

  "@class" :            "org.apereo.cas.services.RegexRegisteredService",

  "serviceId" :         ".*",

  "name" :              "localhost",

  "id" :                1,

  "evaluationOrder" :   1,

  "accessStrategy" : {

    "@class" : "org.apereo.cas.services.DefaultRegisteredServiceAccessStrategy",

    "enabled" : true,

    "ssoEnabled" : true

  },

  "attributeReleasePolicy" : {

    "@class" : "org.apereo.cas.services.ReturnAllAttributeReleasePolicy"

  }

}

I fire up my casified application and point it to my new cas install. 

I get redirected to cas for login: https://localhost:8443/auth/login?TARGET=https%3A%2F%2Flocalhost%3A9443%2Fsample%2Fsecured%2Findex.jsp

I am able to log into this new cas instance but it does not redirect me back to my application. It remains on the cas "Log In Successful" page with a message "...you are seeing this page because CAS does not know about your target destination and how to get you there..."

What am I missing here?

-psv

[Pablo Vidaurri]

Btw, i do see the service being loaded every minute in the log:    <Adding registered service [.*]>

[Misagh Moayyed]

Is your client application sending a SAML1 authentication request to CAS? 

[Pablo Vidaurri]

Yes, I'm using Saml11AuthenticationFilter in my cas client application 

[Pablo Vidaurri]

I added 

 compile "org.apereo.cas:cas-server-support-saml:${project.'cas.version'}"

getting further but interestingly, the look/feel of the login page change. 

Looks like it will work now, just need to get past the cert issue

On Friday, March 29, 2019 at 5:14:37 PM UTC-5, Misagh Moayyed wrote:

[Jon Anderson]

I would try a real url in the service Id, and I think that the id inside the file is supposed to match the id in the file name.

---

From: cas-...@apereo.org [cas-...@apereo.org] on behalf of Pablo Vidaurri [psvid...@gmail.com]
Sent: Friday, March 29, 2019 3:12 PM
To: CAS Community
Subject: [cas-user] New install of Cas 6.1.0, json service not working

--
- 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+u...@apereo.org.
To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/e3a8b049-8ea5-436d-8b86-cedadcd0f473%40apereo.org.

[Pablo Vidaurri]

I actually got it to work with serviceId .* after I provided the saml11 dependency.

the name value should be part of the filename, not the serviceid

Now I can put in a proper serviceId.

To unsubscribe from this group and stop receiving emails from it, send an email to cas...@apereo.org.