[cas-user] Re: CAS 5.2.0 How to configure cas in that way so that it listen to HTTP?

Hello Jozef that's my current configuration: cas.server.httpProxy.enabled=true cas.server.httpProxy.secure=true cas.server.httpProxy.protocol=AJP/1.3 cas.server.httpProxy.scheme=http cas.server.httpProxy.redirectPort=8080 cas.server.httpProxy.proxyPort=8080

[cas-user] how to access admin or management page?

I am running CAS 5.2 and have configured ldap for authentication. But I still have not figured out how to access the admin or management page. What do I need to configure to login to the management page? Do I need to define an admin account? Do I need to define the Admin Status Endpoints per

Re: [cas-user] JSON Service Registry cas.serviceRegistry.config.location property setting ineffective after upgrading to CAS version 5.2

You have the wrong property name (I forget when it changed). cas.serviceRegistry.json.location: file:/etc/cas/services Also, since you have your own non-empty service registry, you should have cas.serviceRegistry.initFromJson: false That property tells the CAS server to load an otherwise

[cas-user] JSON Service Registry cas.serviceRegistry.config.location property setting ineffective after upgrading to CAS version 5.2

I updated my test sever from CAS v5.1.4 to v5.2.0, and my configruation is no longer reading my *.json files from my external file location. Here are my relevant property settings: # # Service Registry #

Re: [cas-user] having difficulty with dependencies when upgrading to CAS 5.2.0

Removing the dependency with the org.ldaptive groupId and ldaptive-unboundid artifactId solved my issue. Thank you, David, for steering my on the right track. Now I have another issue related to my cas.serviceRegistry.config.location property setting not working, but I will post that in a

[cas-user] Re: How to specify landing page (url) in json file for a service when accessStrategy requiredAttributes results in "Service Access Denied"

Just to confirm: upgrading to CAS v5.2 fixed the unauthorizedRedirectUrl property. Thanks! On Wednesday, December 13, 2017 at 9:02:59 AM UTC-5, crdaudt wrote: > > Just a quick update. I have not yet been able to verify Jeremy's idea > about v5.2 fixing the "unauthorizedRedirectUrl" property.

Re: [cas-user] CAS 5.2.0 Falied adding ticket in Memcached Ticket Registry Key is too long (maxlen = 250)

Hi, It's a matter of extra security via signing and encryption, not directly a matter of size. So you can disable the encryption and signature of the TGT via the appropriate properties: cas.tgc.crypto.encryption.key= and cas.tgc.crypto.signing.key= Leave them blank. Thanks. Best regards, Jérôme

Re: [cas-user] CAS 5.2 configuration to delegate authentication to SAML IdP [Octa] through SAML 2.0

Thanks for the prompt answer. I actually want the file name where I should put the properties. Consider I have CAS 5.2 deployed to Tomcat. I see two properties files in tomcat8/webapps/cas\WEB-INF\classes 1. bootstrap.properties 2. application.properties In which file should I put the

Re: [cas-user] CAS 5.2.0 Falied adding ticket in Memcached Ticket Registry Key is too long (maxlen = 250)

no i don't need the TGC too long, how can I make it shorter? On Monday, December 18, 2017 at 5:37:09 PM UTC+8, leleuj wrote: > > Hi, > > The encryption of the TGC makes it too long for a Memcached key: do you > really need it? > Thanks. > Best regards, > Jérôme > > > On Mon, Dec 18, 2017 at 9:58

[cas-user] Re: CAS 5.2 configuration to delegate authentication to SAML IdP [Octa] through SAML 2.0

For setting up SAML application in Octa I referred to - https://developer.okta.com/standards/SAML/setting_up_a_saml_application_in_okta On Monday, 18 December 2017 15:06:14 UTC+5:30, Ravikumar Ganugapanta wrote: > > Hi, > > I am new to SAML, and I am trying out how to configure CAS for

Re: [cas-user] CAS 5.2 configuration to delegate authentication to SAML IdP [Octa] through SAML 2.0

Hi, This is the properties to configure: https://apereo.github.io/cas/5.2.x/installation/Configuration-Properties.html#saml Follow this example: https://github.com/pac4j/spring-webmvc-pac4j-boot-demo/blob/master/src/main/java/org/pac4j/demo/spring/Pac4jConfig.java#L59 Thanks. Best regards,

Re: [cas-user] CAS 5.2.0 Falied adding ticket in Memcached Ticket Registry Key is too long (maxlen = 250)

Hi, The encryption of the TGC makes it too long for a Memcached key: do you really need it? Thanks. Best regards, Jérôme On Mon, Dec 18, 2017 at 9:58 AM, casuser wrote: > > > *This is my cas.properties, *# cas.tgc.path= > cas.tgc.maxAge=-1 > # cas.tgc.domain= >

[cas-user] CAS 5.2 configuration to delegate authentication to SAML IdP [Octa] through SAML 2.0

Hi, I am new to SAML, and I am trying out how to configure CAS for delegating the authentication to an Identity Provider [Octa] using SAML 2.0 I have configured the identity provider, now I am not getting how to configure CAS to delegate the authentication. I have the CAS 5.2 WAR overlay, and

[cas-user] CAS 5.2.0 Falied adding ticket in Memcached Ticket Registry Key is too long (maxlen = 250)

*This is my cas.properties, *# cas.tgc.path= cas.tgc.maxAge=-1 # cas.tgc.domain= cas.tgc.signingKey=*** cas.tgc.name=TGC