[cas-user] override cas.example.org DNS name

2020-12-21 Thread cheekian yap
Hi, cas version: 6.2.6 I have added the following line inside application.properties: cas.authn.saml-idp.entity-id=https://xx.xx.xx.xx:8443/cas/idp/metadata However, the certificate generated in /etc/cas/saml/idp-metadata.xml still shows: X509v3 Subject Alternative Name: DNS:ca

[cas-user] Re: simplesamlphp sp integreate with apereo cas idp

2020-12-21 Thread cheekian yap
I think i have figure out the problem. the other service json file is too generic: { "@class" : "org.apereo.cas.services.RegexRegisteredService", "serviceId" : ".*", "name" : "booking", "id" : 1 } This will override saml sp json file. cheekian yap 在 2020年12月22日 星期二上午11:20:51 [UTC+8] 的信中

[cas-user] Re: simplesamlphp sp integreate with apereo cas idp

2020-12-21 Thread cheekian yap
I managed to get my saml sp registered on service registry. The scenario is: Originally I have 2 json file in my classpath:/services. One of the them is saml sp. Somehow when I removed the other one, saml sp was able to be registered. So my question become how to add 2 services simultaneously

[cas-user] simplesamlphp sp integreate with apereo cas idp

2020-12-21 Thread cheekian yap
Hi, Cas version 6.2.6 I got this error message when being redirected from sp site to cas: WARN [org.apereo.cas.support.saml.web.idp.profile.AbstractSamlIdPProfileHandlerController] - <[http://xx.xx.xx.xx] is not found in the registry or service access is denied. Ensure service is registered

Re: [cas-user] How to connect cas server 6.2 to mod_auth_cas apache client using ubuntu

2020-12-21 Thread arti wavale
Hello, Created certificate using following command: 1] keytool -genkey -alias cas -keyalg RSA -validity 999 -keystore /etc/cas/thekeystore -ext san=dns:$REPLACE_WITH_FULL_MACHINE_NAME 2] keytool -export -file /etc/cas/config/cas.crt -keystore /etc/cas/thekeystore -alias cas 3] sudo keytool -imp

[cas-user] Re: CAS-OIDC ClientId Introspection Response

2020-12-21 Thread Frédéric Lohier
Hello, I am using CAS 6.2.5 and I also noticed the same issue. When I make a request to the /introspect endpoint with an access_token as parameter and basic authorization header with client_id:client_secret, the "client-id" claim of the introspect response contains the client_id I passed in the