Hello everyone,
I still have that error:Application not authorized to use CAS
Here are my conf files :
/home/ahmed/cas-server-4.0.0/cas-management-webapp/src/main/webapp/WEB-INF/managementConfigContext.xml
:
<?xml version="1.0" encoding="UTF-8"?>
<!--
Licensed to Jasig under one or more contributor license
agreements. See the NOTICE file distributed with this work
for additional information regarding copyright ownership.
Jasig licenses this file to you under the Apache License,
Version 2.0 (the "License"); you may not use this file
except in compliance with the License. You may obtain a
copy of the License at the following location:
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
-->
<!--
| managementConfigContext.xml centralizes into one file some of the
declarative configuration that
| all CAS deployers will need to modify for the (services) management
webapp.
|
| The beans declared in this file are instantiated at context
initialization time by the Spring
| ContextLoaderListener declared in web.xml. It finds this file because
this
| file is among those declared in the context parameter
"contextConfigLocation".
+-->
<beans xmlns="http://www.springframework.org/schema/beans";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xmlns:p="http://www.springframework.org/schema/p";
xmlns:c="http://www.springframework.org/schema/c";
xmlns:tx="http://www.springframework.org/schema/tx";
xmlns:sec="http://www.springframework.org/schema/security";
xmlns:util="http://www.springframework.org/schema/util";
xsi:schemaLocation="http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd
http://www.springframework.org/schema/tx
http://www.springframework.org/schema/tx/spring-tx.xsd
http://www.springframework.org/schema/util
http://www.springframework.org/schema/util/spring-util.xsd
http://www.springframework.org/schema/security
http://www.springframework.org/schema/security/spring-security.xsd";>
<!--
This bean defines the security roles for the Services Management
application. Simple deployments can use the in-memory version.
More robust deployments will want to use another option, such as the Jdbc
version.
The name of this should remain "userDetailsService" in order for Spring
Security to find it.
-->
<sec:user-service id="userDetailsService"
properties="${user.details.file.location:classpath:user-details.properties}" />
<!--
Bean that defines the attributes that a service may return. This example
uses the Stub/Mock version. A real implementation
may go against a database or LDAP server. The id should remain
"attributeRepository" though.
-->
<bean id="attributeRepository"
class="org.jasig.services.persondir.support.StubPersonAttributeDao"
p:backingMap-ref="backingMap">
</bean>
<util:map id="backingMap">
<entry key="uid" value="uid" />
<entry key="eduPersonAffiliation" value="eduPersonAffiliation" />
<entry key="groupMembership" value="groupMembership" />
</util:map>
<!--
Sample, in-memory data store for the ServiceRegistry. A real implementation
would probably want to replace this with the JPA-backed ServiceRegistry DAO
The name of this bean should remain "serviceRegistryDao".
-->
<bean id="serviceRegistryDao"
class="org.jasig.cas.adaptors.ldap.services.LdapServiceRegistryDao"
p:connectionFactory-ref="pooledLdapConnectionFactory"
p:searchRequest-ref="searchRequest"
p:ldapServiceMapper-ref="ldapMapper" />
<bean id="ldapMapper"
class="org.jasig.cas.adaptors.ldap.services.DefaultLdapServiceMapper"/>
<util:list id="registeredServicesList">
<bean class="org.jasig.cas.services.RegexRegisteredService"
p:id="1" p:name="HTTP and IMAP" p:description="Allows HTTP(S) and
IMAP(S$
p:serviceId="^(https?|imaps?)://localhost:8443/cas*"
p:evaluationOrder="10000001" />
<!--
Use the following definition instead of the above to
further restrict access
to services within your domain (including subdomains).
Note that example.com must be replaced with the domain you
wish to permit.
-->
<bean
class="org.jasig.cas.services.RegexRegisteredService">
<property name="id" value="1" />
<property name="name" value="HTTP and IMAP on
https://localhost:8443/cas"; $
<property name="description" value="Allows HTTP(S) and IMAP(S)
protocols o$
<property name="serviceId"
value="^(https?|imaps?)://([A-Za-z0-9_-]+\.)*ht$
<property name="evaluationOrder" value="0" />
<property name="attributeFilter">
<bean
class="org.jasig.cas.services.support.RegisteredServiceRegexAttrib$
</property>
</bean>
</util:list>
</property>
</bean>
<bean id="auditTrailManager"
class="com.github.inspektr.audit.support.Slf4jLoggingAuditTrailManager" />
</beans>
and
/home/ahmed/cas-server-4.0.0/cas-management-webapp/src/main/webapp/WEB-INF/managementConfigContext.xml
:
<?xml version="1.0" encoding="UTF-8"?>
<!--
Licensed to Jasig under one or more contributor license
agreements. See the NOTICE file distributed with this work
for additional information regarding copyright ownership.
Jasig licenses this file to you under the Apache License,
Version 2.0 (the "License"); you may not use this file
except in compliance with the License. You may obtain a
copy of the License at the following location:
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
-->
<!--
| deployerConfigContext.xml centralizes into one file some of the declarative
configuration that
| all CAS deployers will need to modify.
|
| This file declares some of the Spring-managed JavaBeans that make up a CAS
deployment.
| The beans declared in this file are instantiated at context initialization
time by the Spring
| ContextLoaderListener declared in web.xml. It finds this file because this
| file is among those declared in the context parameter "contextConfigLocation".
|
| By far the most common change you will need to make in this file is to change
the last bean
| declaration to replace the default authentication handler with
| one implementing your approach for authenticating usernames and passwords.
+-->
<beans xmlns="http://www.springframework.org/schema/beans";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xmlns:p="http://www.springframework.org/schema/p";
xmlns:c="http://www.springframework.org/schema/c";
xmlns:tx="http://www.springframework.org/schema/tx";
xmlns:util="http://www.springframework.org/schema/util";
xmlns:sec="http://www.springframework.org/schema/security";
xsi:schemaLocation="http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans-3.2.xsd
http://www.springframework.org/schema/tx
http://www.springframework.org/schema/tx/spring-tx-3.2.xsd
http://www.springframework.org/schema/security
http://www.springframework.org/schema/security/spring-security-3.2.xsd
http://www.springframework.org/schema/util
http://www.springframework.org/schema/util/spring-util.xsd";>
<!--
| The authentication manager defines security policy for authentication
by specifying at a minimum
| the authentication handlers that will be used to authenticate
credential. While the AuthenticationManager
| interface supports plugging in another implementation, the default
PolicyBasedAuthenticationManager should
| be sufficient in most cases.
+-->
<bean id="authenticationManager"
class="org.jasig.cas.authentication.PolicyBasedAuthenticationManager">
<constructor-arg>
<map>
<!--
| IMPORTANT
| Every handler requires a unique name.
| If more than one instance of the same handler class is
configured, you must explicitly
| set its name to something other than its default name
(typically the simple class name).
-->
<entry key-ref="proxyAuthenticationHandler"
value-ref="proxyPrincipalResolver" />
<entry key-ref="primaryAuthenticationHandler"
value-ref="primaryPrincipalResolver" />
</map>
</constructor-arg>
<!-- Uncomment the metadata populator to allow clearpass to capture and
cache the password
This switch effectively will turn on clearpass.
<property name="authenticationMetaDataPopulators">
<util:list>
<bean
class="org.jasig.cas.extension.clearpass.CacheCredentialsMetaDataPopulator"
c:credentialCache-ref="encryptedMap" />
</util:list>
</property>
-->
<!--
| Defines the security policy around authentication. Some
alternative policies that ship with CAS:
|
| * NotPreventedAuthenticationPolicy - all credential must either
pass or fail authentication
| * AllAuthenticationPolicy - all presented credential must be
authenticated successfully
| * RequiredHandlerAuthenticationPolicy - specifies a handler that
must authenticate its credential to pass
-->
<property name="authenticationPolicy">
<bean class="org.jasig.cas.authentication.AnyAuthenticationPolicy"
/>
</property>
</bean>
<!-- Required for proxy ticket mechanism. -->
<bean id="proxyAuthenticationHandler"
class="org.jasig.cas.authentication.handler.support.HttpBasedServiceCredentialsAuthenticationHandler"
p:httpClient-ref="httpClient" />
<!--
| TODO: Replace this component with one suitable for your enviroment.
|
| This component provides authentication for the kind of credential used
in your environment. In most cases
| credential is a username/password pair that lives in a system of
record like an LDAP directory.
| The most common authentication handler beans:
|
| * org.jasig.cas.authentication.LdapAuthenticationHandler
| * org.jasig.cas.adaptors.jdbc.QueryDatabaseAuthenticationHandler
| *
org.jasig.cas.adaptors.x509.authentication.handler.support.X509CredentialsAuthenticationHandler
| *
org.jasig.cas.support.spnego.authentication.handler.support.JCIFSSpnegoAuthenticationHandler
-->
<bean id="primaryAuthenticationHandler"
class="org.jasig.cas.authentication.AcceptUsersAuthenticationHandler">
<property name="users">
<map>
<entry key="casuser" value="Mellon"/>
</map>
</property>
</bean>
<!-- Required for proxy ticket mechanism -->
<bean id="proxyPrincipalResolver"
class="org.jasig.cas.authentication.principal.BasicPrincipalResolver"
/>
<!--
| Resolves a principal from a credential using an attribute repository
that is configured to resolve
| against a deployer-specific store (e.g. LDAP).
-->
<bean id="primaryPrincipalResolver"
class="org.jasig.cas.authentication.principal.PersonDirectoryPrincipalResolver"
>
<property name="attributeRepository" ref="attributeRepository" />
</bean>
<sec:ldap-server id="ldapServer" url="https://localhost:8443/cas";
manager-dn="cn=adminusername,cn=Users,dc=london-scottish,dc=com"
manager-password="mypassword" />
<sec:ldap-user-service id="userDetailsService" server-ref="ldapServer"
group-search-base="cn=Groups,dc=mycompany,dc=com"
group-role-attribute="cn"
group-search-filter="(uniquemember={0})"
user-search-base="cn=Users,dc=mycompany,dc=com"
user-search-filter="(uid={0})"/>
<!--
Bean that defines the attributes that a service may return. This example
uses the Stub/Mock version. A real implementation
may go against a database or LDAP server. The id should remain
"attributeRepository" though.
+-->
<bean id="attributeRepository"
class="org.jasig.services.persondir.support.StubPersonAttributeDao"
p:backingMap-ref="attrRepoBackingMap" />
<util:map id="attrRepoBackingMap">
<entry key="uid" value="uid" />
<entry key="eduPersonAffiliation" value="eduPersonAffiliation" />
<entry key="groupMembership" value="groupMembership" />
</util:map>
<!--
Sample, in-memory data store for the ServiceRegistry. A real implementation
would probably want to replace this with the JPA-backed ServiceRegistry DAO
The name of this bean should remain "serviceRegistryDao".
+-->
<bean id="serviceRegistryDao"
class="org.jasig.cas.services.InMemoryServiceRegistryDaoImpl"
p:registeredServices-ref="registeredServicesList" />
<util:list id="registeredServicesList">
<bean class="org.jasig.cas.services.RegexRegisteredService"
p:id="1" p:name="HTTP and IMAP" p:description="Allows HTTP(S) and
IMAP(S) protocols"
p:serviceId="^(https?|imaps?)://localhost:8443/cas*"
p:evaluationOrder="10000001" />
<!--
Use the following definition instead of the above to further restrict
access
to services within your domain (including sub domains).
Note that example.com must be replaced with the domain you wish to
permit.
This example also demonstrates the configuration of an attribute filter
that only allows for attributes whose length is 3.
-->
<bean class="org.jasig.cas.services.RegexRegisteredService">
<property name="id" value="1" />
<property name="name" value="HTTP and IMAP on
https://localhost:8443/cas"; />
<property name="description" value="Allows HTTP(S) and IMAP(S)
protocols on https://localhost:8443/cas"; />
<property name="serviceId"
value="^(https?|imaps?)://([A-Za-z0-9_-]+\.)*https://localhost:8443/cas/.*"; />
<property name="evaluationOrder" value="0" />
<property name="attributeFilter">
<bean
class="org.jasig.cas.services.support.RegisteredServiceRegexAttributeFilter"
c:regex="^\w{3}$" />
</property>
</bean>
</util:list>
<bean id="auditTrailManager"
class="com.github.inspektr.audit.support.Slf4jLoggingAuditTrailManager" />
<bean id="healthCheckMonitor"
class="org.jasig.cas.monitor.HealthCheckMonitor" p:monitors-ref="monitorsList"
/>
<util:list id="monitorsList">
<bean class="org.jasig.cas.monitor.MemoryMonitor"
p:freeMemoryWarnThreshold="10" />
<!--
NOTE
The following ticket registries support SessionMonitor:
* DefaultTicketRegistry
* JpaTicketRegistry
Remove this monitor if you use an unsupported registry.
-->
<bean class="org.jasig.cas.monitor.SessionMonitor"
p:ticketRegistry-ref="ticketRegistry"
p:serviceTicketCountWarnThreshold="5000"
p:sessionCountWarnThreshold="100000" />
</util:list>
<tx:annotation-driven transaction-manager-ref="transactionManager" />
<bean id="factoryBean"
class="org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean"
p:dataSource-ref="dataSource"
p:jpaVendorAdapter-ref="jpaVendorAdapter"
p:packagesToScan-ref="packagesToScan">
<property name="jpaProperties">
<props>
<prop key="hibernate.dialect">${database.dialect}</prop>
<prop key="hibernate.hbm2ddl.auto">update</prop>
<prop key="hibernate.jdbc.batch_size">${database.batchSize}</prop>
</props>
</property>
</bean>
<bean id="jpaVendorAdapter"
class="org.springframework.orm.jpa.vendor.HibernateJpaVendorAdapter"
p:generateDdl="true"
p:showSql="true" />
<bean id="serviceRegistryDao"
class="org.jasig.cas.services.JpaServiceRegistryDaoImpl" />
<bean id="transactionManager"
class="org.springframework.orm.jpa.JpaTransactionManager"
p:entityManagerFactory-ref="factoryBean" />
<!--
| Injects EntityManager/Factory instances into beans with
| @PersistenceUnit and @PersistenceContext
-->
<bean
class="org.springframework.orm.jpa.support.PersistenceAnnotationBeanPostProcessor"
/>
<!--
Configuration via JNDI
-->
<bean id="dataSource" class="org.springframework.jndi.JndiObjectFactoryBean"
p:jndiName="java:comp/env/jdbc/cas-source" />
</beans>
Anyone who can advise me what am I doing wrong and advise me what to do next in
order to authenticate KOHA with CAS. Thanks for helping !
Ahmed
From: [email protected]
To: [email protected]
Subject: FW: [cas-user] Application not authorized to use CAS
Date: Thu, 7 May 2015 01:20:32 +0200
From: [email protected]
To: [email protected]
Subject: RE: [cas-user] Application not authorized to use CAS
Date: Thu, 7 May 2015 01:19:41 +0200
Yes, i can login to CAS when I omit that piece of code, maybe I put it in the
wrong section of the file. When I add it, I get the error 404(service is
unavailable). In KOHA (CAS settings) I set CAS Server Url to be:
https://localhost:8443/cas and when I'm trying to access that over KOHA user
login(if you have CAS account click here) I get the error: Application is not
authorized to use CAS. I hope I explained my problem well enough.
Ahmed
Date: Wed, 6 May 2015 12:58:26 -0500
From: [email protected]
To: [email protected]; [email protected]
Subject: Re: [cas-user] Application not authorized to use CAS
Just for clarification - things work correctly when you omit this piece of code:
<sec:ldap-server id="ldapServer" url="ldap://myserver:13060/";
manager-dn="cn=adminusername,cn=Users,dc=london-scottish,dc=com"
manager-password="mypassword" />
<sec:ldap-user-service id="userDetailsService" server-ref="ldapServer"
group-search-base="cn=Groups,dc=mycompany,dc=com"
group-role-attribute="cn"
group-search-filter="(uniquemember={0})"
user-search-base="cn=Users,dc=mycompany,dc=com"
user-search-filter="(uid={0})"/>
but fail once you add it? And to be sure, the error message that you're
receiving is the "application not authorized to use CAS" message?
The reason I'm curious is because that chunk of code there has absolutely
nothing to do with an application talking to CAS; it's strictly for user-side
things.
Chris
>>> Ahmed Hadzic <[email protected]> 05/06/15 10:03 AM >>>
Hello all,
I am about to graduate and for my senior design project I have to integrate CAS
with KOHA (Open ILS). I am using Ubuntu server 14.04, so far I made secure
connection for CAS, and now i need to login to CAS as KOHA user. This is where
I encountered problems. I found out that I need to get the CAS server's Manager
to add the OPAC Url to the Service management system in CAS itself.
When I try to access over browser(https://localhost:8443/cas/services) I get
redirected to CAS login page. I followed this documentation:
http://jasig.github.io/cas/4.0.x/installation/Service-Management.html.
Since I am pretty much newbie for CAS I would be thankful if you could help me.
Here are the details of what I did from the guide above:
LdapServiceRegistryDao
<bean id="serviceRegistryDao"
class="org.jasig.cas.adaptors.ldap.services.LdapServiceRegistryDao"
p:connectionFactory-ref="pooledLdapConnectionFactory"
p:searchRequest-ref="searchRequest"
p:ldapServiceMapper-ref="ldapMapper" />
<bean id="ldapMapper"
class="org.jasig.cas.adaptors.ldap.services.DefaultLdapServiceMapper"/>
I added this in
/home/ahmed/cas-server-4.0.0/cas-management-webapp/src/main/webapp/WEB-INF/managementConfigContext.xml
JpaServiceRegistryDaoImpl
<tx:annotation-driven transaction-manager-ref="transactionManager" />
<bean id="factoryBean"
class="org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean"
p:dataSource-ref="dataSource"
p:jpaVendorAdapter-ref="jpaVendorAdapter"
p:packagesToScan-ref="packagesToScan">
<property name="jpaProperties">
<props>
<prop key="hibernate.dialect">${database.dialect}</prop>
<prop key="hibernate.hbm2ddl.auto">update</prop>
<prop key="hibernate.jdbc.batch_size">${database.batchSize}</prop>
</props>
</property>
</bean>
<bean id="jpaVendorAdapter"
class="org.springframework.orm.jpa.vendor.HibernateJpaVendorAdapter"
p:generateDdl="true"
p:showSql="true" />
<bean id="serviceRegistryDao"
class="org.jasig.cas.services.JpaServiceRegistryDaoImpl" />
<bean id="transactionManager"
class="org.springframework.orm.jpa.JpaTransactionManager"
p:entityManagerFactory-ref="factoryBean" />
<!--
| Injects EntityManager/Factory instances into beans with
| @PersistenceUnit and @PersistenceContext
-->
<bean
class="org.springframework.orm.jpa.support.PersistenceAnnotationBeanPostProcessor"
/>
<!--
Configuration via JNDI
-->
<bean id="dataSource" class="org.springframework.jndi.JndiObjectFactoryBean"
p:jndiName="java:comp/env/jdbc/cas-source" />
I added this in
/home/ahmed/cas-server-4.0.0/cas-server-webapp/src/main/webapp/WEB-INF/deployerConfigContext.xml
Installing the Services Management Webapp
<dependency>
<groupId>org.jasig.cas</groupId>
<artifactId>cas-management-webapp</artifactId>
<version>${cas.version}</version>
<type>war</type>
<scope>runtime</scope>
</dependency>
Added this in
/home/ahmed/cas-server-4.0.0/cas-management-webapp/pom.xml
Spring-security-ldap
<dependency>
<groupId>org.springframework.security</groupId>
<artifactId>spring-security-ldap</artifactId>
<version>${spring.security.ldap.version}</version>
<exclusions>
<exclusion>
<groupId>org.springframework</groupId>
<artifactId>spring-aop</artifactId>
</exclusion>
<exclusion>
<groupId>org.springframework</groupId>
<artifactId>spring-tx</artifactId>
</exclusion>
<exclusion>
<groupId>org.springframework</groupId>
<artifactId>spring-beans</artifactId>
</exclusion>
<exclusion>
<groupId>org.springframework</groupId>
<artifactId>spring-context</artifactId>
</exclusion>
<exclusion>
<groupId>org.springframework</groupId>
<artifactId>spring-core</artifactId>
</exclusion>
</exclusions>
</dependency>
Added this in
/home/ahmed/cas-server-4.0.0/cas-management-webapp/pom.xml
My CAS fails when I add this part to
/var/lib/tomcat7/webapps/cas/WEB-INF/deployerConfigContext.xml
<sec:ldap-server id="ldapServer" url="ldap://myserver:13060/";
manager-dn="cn=adminusername,cn=Users,dc=london-scottish,dc=com"
manager-password="mypassword" />
<sec:ldap-user-service id="userDetailsService" server-ref="ldapServer"
group-search-base="cn=Groups,dc=mycompany,dc=com"
group-role-attribute="cn"
group-search-filter="(uniquemember={0})"
user-search-base="cn=Users,dc=mycompany,dc=com"
user-search-filter="(uid={0})"/>
I don't quite understand this and I don't know if I am doing things right, so
any help is very much appreciated.
Kind regards,
Ahmed
--
You are currently subscribed to [email protected] as:
[email protected]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/cas-user
--
You are currently subscribed to [email protected] as:
[email protected]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/cas-user
--
You are currently subscribed to [email protected] as:
[email protected]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/cas-user
