RADIUS integration with built-in CAS

By: Conan Malone user 14 Dec 2016 at 4:17 a.m. CST

1 Response
Conan Malone gravatar
Is it possible to add RADIUS configuration with GLUUs built in CAS? For example we have a CAS server and to add RADIUS config we needed to add a dependency to the pom.xml file <dependency> <groupId>org.jasig.cas</groupId> <artifactId>cas-server-support-radius</artifactId> <version>${cas.version}</version> </dependency> then add to deployerConfigContext <alias name="radiusAuthenticationHandler" alias="primaryAuthenticationHandler" /> then finally add in the RADIUS settings to cas.properties cas.radius.client.inetaddr=ourRADIUSserver cas.radius.client.port.acct=1813 cas.radius.client.socket.timeout=60 cas.radius.client.port.authn=1812 cas.radius.client.sharedsecret=**************** is all of this possible to do within the built in cas for GLUU? and if so where do each of these files exist within the server? cas.properties deployerConfigContext.xml pom.xml Thanks in advance, Conan
CentOS72
closed

Answers

By Mohib Zico staff 14 Dec 2016 at 6:19 a.m. CST

Copy
Mohib Zico gravatar
Yes, Possible. CAS configurations are in two section: - CAS configuration files inside /opt/tomcat/webapps/cas/ ( inside Gluu Server container ) - Inside LDAP: 'ou=oxcas,ou=configuration,inum=@abcd....,ou=appliances,o=gluu' However as Gluu Server is unified login ( CAS/SAML/OpenID Connect ) and there is no out of the box radius script in community edition; so you can write a [custom authentication interception script](https://gluu.org/docs/customize/script/) that uses a RADIUS API in python or Java.

Post an answer