Unless you circumvent CAS security, it will only issue proxy granting tickets over HTTPS. Your configuration looks like HTTP. That's what the error in your log is about.
The reason you need to log in again is different, but related. CAS will not maintain a single sign-on session unless you have logged in over HTTPS. Again, you could circumvent CAS security, but that is not recommended. Adam lai seong au wrote: > The CAS server got error after login. It work like normal but the CAS > will not store the user session. I detected it because i found it need > to relogin after i restart myapp's tomcat. But the CAS server should > maintain the user session is not it? > > INFO: Server startup in 26742 ms > 2009-12-14 23:31:31,783 INFO > [org.jasig.cas.web.flow.InitialFlowSetupAction] - <Setting path for > cookies to: /cas-server-webapp-3.3.3> > 2009-12-14 23:31:41,625 INFO > [org.jasig.cas.authentication.AuthenticationManagerImpl] - > <AuthenticationHandler: > org.jasig.cas.adaptors.jdbc.SearchModeSearchDatabaseAuthenticationHandler > successfully authenticated the user which provided the following > credentials: [username: SUREWIN]> > 2009-12-14 23:31:41,635 INFO > [org.jasig.cas.CentralAuthenticationServiceImpl] - <Granted service > ticket [ST-1-70doLiPdi3zoQzVl9FRX-cas] for service > [http://localhost:8080/myapp/j_spring_cas_security_check] for user > [SUREWIN]> > 2009-12-14 23:31:41,716 ERROR > [org.jasig.cas.web.ServiceValidateController] - <TicketException > generating ticket for: [callbackUrl: > http://localhost:8080/myapp/secure/receptor]> > org.jasig.cas.ticket.TicketCreationException: > error.authentication.credentials.unsupported > > > > <?xml version="1.0" encoding="UTF-8"?> > <beans xmlns="http://www.springframework.org/schema/beans"; > xmlns:sec="http://www.springframework.org/schema/security"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xsi:schemaLocation="http://www.springframework.org/schema/beans > http://www.springframework.org/schema/beans/spring-beans-2.0.xsd > http://www.springframework.org/schema/security > http://www.springframework.org/schema/security/spring-security-2.0.xsd > <http://www.springframework.org/schema/security/spring-security-2.0..xsd>"> > > <sec:http entry-point-ref="casProcessingFilterEntryPoint"> > <sec:intercept-url pattern="/secure/extreme/**" > access="ROLE_SUPERVISOR" requires-channel="https" /> > <sec:intercept-url pattern="/pages/templates/**" > access="ROLE_ADM,ROLE_USR" /> > <sec:intercept-url pattern="/pages/secure/**" > access="ROLE_ADM,ROLE_USR" /> > <sec:intercept-url pattern="/pages/user/admin/**" > access="ROLE_ADM" /> > <sec:intercept-url pattern="/pages/user/personal/**" > access="ROLE_ADM,ROLE_USR" /> > > <sec:logout logout-success-url="/cas-logout.jsp"/> > </sec:http> > <sec:authentication-manager alias="authenticationManager"/> > > <bean id="casProcessingFilter" > class="org.springframework.security.ui.cas.CasProcessingFilter"> > <sec:custom-filter after="CAS_PROCESSING_FILTER" /> > <property name="authenticationManager" > ref="authenticationManager"/> > <property name="authenticationFailureUrl" value="/casfailed.jsp"/> > <property name="defaultTargetUrl" value="/"/> > <property name="proxyGrantingTicketStorage" > ref="proxyGrantingTicketStorage" /> > <property name="proxyReceptorUrl" value="/secure/receptor" /> > </bean> > > <bean id="roleBaseRedirectUrl" > class="com.moliscwebos.framework.acegi.RoleBaseRedirectUrl"> > <sec:custom-filter after="LAST"/> > <property name="rolePathMapping"> > <list> > <value>ROLE_ADM,ROLE_TEST=/pages/templates/main.admin.jsf</value> > <value>ROLE_USR=/pages/templates/main.user.jsf</value> > <value>ROLE_TEST=/pages/templates/main.sss.jsf</value> > </list> > </property> > <property name="fromUrl"> > <value>/main.jsf</value> > </property> > <property name="defaultUrl"><value>/default.jsp</value></property> > </bean> > > <bean id="casProcessingFilterEntryPoint" > class="org.springframework..security.ui.cas.CasProcessingFilterEntryPoint"> > <property name="loginUrl" > value="http://localhost/cas-server-webapp-3.3.3/login"/ > <http://localhost/cas-server-webapp-3.3.3/login%22/>> > <property name="serviceProperties" ref="serviceProperties"/> > </bean> > <bean id="casAuthenticationProvider" > class="org.springframework.security.providers.cas.CasAuthenticationProvider"> > <sec:custom-authentication-provider /> > <property name="userDetailsService" ref="userService"/> > <property name="serviceProperties" ref="serviceProperties" /> > <property name="ticketValidator"> > <bean > class="org.jasig.cas.client.validation.Cas20ServiceTicketValidator"> > <constructor-arg index="0" > value="http://localhost/cas-server-webapp-3.3.3"; /> > <property name="proxyGrantingTicketStorage" > ref="proxyGrantingTicketStorage" /> > <property name="proxyCallbackUrl" > value="http://localhost:8080/myapp/secure/receptor"; /> > </bean> > </property> > <property name="key" value="an_id_for_this_auth_provider_only"/> > </bean> > > <bean id="proxyGrantingTicketStorage" > class="org.jasig.cas.client.proxy.ProxyGrantingTicketStorageImpl" /> > <bean id="serviceProperties" > class="org.springframework.security.ui.cas.ServiceProperties"> > <property name="service" > value="http://localhost:8080/myapp/j_spring_cas_security_check"/ > <http://localhost:8080/myapp/j_spring_cas_security_check%22/>> > <property name="sendRenew" value="false"/> > </bean> > > <bean id="user2Dao" > class="com.myapp.framework.user.dao.hibernate.UserDaoImpl" > autowire="byName" /> > <bean id="userRole2Dao" > class="com.myapp.framework.user.dao.hibernate.UserRoleDaoImpl" > autowire="byName" /> > > <bean id="userService" > class="com.myapp.framework.user.dao.hibernate.AuthenticationDaoImpl"> > <property name="userDao" ref="user2Dao"/> > <property name="userRoleDao" ref="userRole2Dao"/> > </bean> > > </beans> > > > > > > > > > > <?xml version="1.0" encoding="UTF-8"?> > <!-- > | 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 > SimpleTestUsernamePasswordAuthenticationHandler 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"; > xsi:schemaLocation="http://www.springframework.org/schema/beans > http://www.springframework.org/schema/beans/spring-beans-2.0.xsd";> > <!-- > | This bean declares our AuthenticationManager. The > CentralAuthenticationService service bean > | declared in applicationContext.xml picks up this > AuthenticationManager by reference to its id, > | "authenticationManager". Most deployers will be able to use the > default AuthenticationManager > | implementation and so do not need to change the class of this > bean. We include the whole > | AuthenticationManager here in the userConfigContext.xml so that > you can see the things you will > | need to change in context. > +--> > <bean id="authenticationManager" > class="org.jasig.cas.authentication.AuthenticationManagerImpl"> > <!-- > | This is the List of CredentialToPrincipalResolvers that identify > what Principal is trying to authenticate.. > | The AuthenticationManagerImpl considers them in order, finding a > CredentialToPrincipalResolver which > | supports the presented credentials. > | > | AuthenticationManagerImpl uses these resolvers for two purposes. > First, it uses them to identify the Principal > | attempting to authenticate to CAS /login . In the default > configuration, it is the DefaultCredentialsToPrincipalResolver > | that fills this role. If you are using some other kind of > credentials than UsernamePasswordCredentials, you will need to replace > | DefaultCredentialsToPrincipalResolver with a > CredentialsToPrincipalResolver that supports the credentials you are > | using. > | > | Second, AuthenticationManagerImpl uses these resolvers to > identify a service requesting a proxy granting ticket. > | In the default configuration, it is the > HttpBasedServiceCredentialsToPrincipalResolver that serves this purpose. > | You will need to change this list if you are identifying services > by something more or other than their callback URL. > +--> > <property name="credentialsToPrincipalResolvers"> > <list> > <!-- > | UsernamePasswordCredentialsToPrincipalResolver supports the > UsernamePasswordCredentials that we use for /login > | by default and produces SimplePrincipal instances conveying the > username from the credentials. > | > | If you've changed your LoginFormAction to use credentials other > than UsernamePasswordCredentials then you will also > | need to change this bean declaration (or add additional > declarations) to declare a CredentialsToPrincipalResolver that > supports the > | Credentials you are using. > +--> > <bean > > class="org.jasig.cas.authentication.principal.UsernamePasswordCredentialsToPrincipalResolver" > > /> > <!-- > | HttpBasedServiceCredentialsToPrincipalResolver supports > HttpBasedCredentials. It supports the CAS 2.0 approach of > | authenticating services by SSL callback, extracting the > callback URL from the Credentials and representing it as a > | SimpleService identified by that callback URL. > | > | If you are representing services by something more or other > than an HTTPS URL whereat they are able to > | receive a proxy callback, you will need to change this bean > declaration (or add additional declarations). > +--> > <bean > > class="org.jasig.cas.authentication.principal.HttpBasedServiceCredentialsToPrincipalResolver" > > /> > </list> > </property> > <!-- > | Whereas CredentialsToPrincipalResolvers identify who it is some > Credentials might authenticate, > | AuthenticationHandlers actually authenticate credentials. Here > we declare the AuthenticationHandlers that > | authenticate the Principals that the > CredentialsToPrincipalResolvers identified. CAS will try these > handlers in turn > | until it finds one that both supports the Credentials presented > and succeeds in authenticating. > +--> > <property name="authenticationHandlers"> > <list> > <!-- > | This is the authentication handler that authenticates services > by means of callback via SSL, thereby validating > | a server side SSL certificate. > + > <bean > class="org.jasig.cas.authentication.handler.support.HttpBasedServiceCredentialsAuthenticationHandler" > p:httpClient-ref="httpClient" /> --> > <bean > class="org.jasig.cas.adaptors.jdbc.SearchModeSearchDatabaseAuthenticationHandler"> > <property name="tableUsers"><value>APP_USER</value></property> > <property name="fieldUser"><value>username</value></property> > <property name="fieldPassword"><value>password</value></property> > <property name="passwordEncoder" ref="passwordEncoder" /> > > > <property name="dataSource" ref="dataSource"/> > </bean> > <!-- > | This is the authentication handler declaration that every CAS > deployer will need to change before deploying CAS > | into production. The default > SimpleTestUsernamePasswordAuthenticationHandler authenticates > UsernamePasswordCredentials > | where the username equals the password. You will need to > replace this with an AuthenticationHandler that implements your > | local authentication strategy. You might accomplish this by > coding a new such handler and declaring > | edu.someschool.its.cas.MySpecialHandler here, or you might use > one of the handlers provided in the adaptors modules. > + > <bean > > class="org.jasig.cas.authentication.handler.support.SimpleTestUsernamePasswordAuthenticationHandler" > > /> > --> </list> > </property> > </bean> > <bean id="passwordEncoder" > class="org.jasig.cas.authentication.handler.DefaultPasswordEncoder"> > <constructor-arg index="0"> <value>MD5</value> </constructor-arg> > </bean> > <bean id="dataSource" class="org.apache.commons.dbcp.BasicDataSource"> > <property name="driverClassName"> > <value>org.postgresql.Driver</value> > </property> > <property name="url"> > <value>jdbc:postgresql://localhost:5432/j6</value> > </property> > <property name="username"><value>postgres</value></property> > <property name="password"><value>password</value></property> > </bean> > <!-- > 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 > Acegi to find it. > > To use this, you should add an entry similar to the following between > the two value tags: > battags=notused,ROLE_ADMIN > > where battags is the username you want to grant access to. You can > put one entry per line. > --> > <bean id="userDetailsService" > class="org.springframework.security.userdetails.memory..InMemoryDaoImpl"> > <property name="userMap"> > <value> > > </value> > </property> > </bean> > > <!-- > 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"> > <property name="backingMap"> > <map> > <entry key="uid" value="uid" /> > <entry key="eduPersonAffiliation" value="eduPersonAffiliation" /> > <entry key="groupMembership" value="groupMembership" /> > </map> > </property> > </bean> > > <!-- > 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" /> > </beans> > > > Jimmy6 > > -- > 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
<<attachment: arybicki.vcf>>
