SSO via CAS in liferay issue ?

[RAVI RAJAMANI, modifié il y a 9 années.]

HI,

I have integrated CAS server and CAS client to liferay. but while i try to login by admin Credinitial the CAS shows following errors

Non-secure Connection

You are currently accessing CAS over a non-secure connection. Single Sign On WILL NOT WORK. In order to have single sign on work, you MUST log in over HTTPS
as shown in image. kindly suggest any solution.



Regards
Ravi

[David H Nebinger, modifié il y a 9 années.]

Solution: Enable https just as it says.

[RAVI RAJAMANI, modifié il y a 9 années.]

I have enable https but it shows SSL connection Error as attached in image.


Regards
Ravi R

[David H Nebinger, modifié il y a 9 années.]

The image says it all, there's ssl connectivity problems. You'll have to resolve those before you can proceed...

[RAVI RAJAMANI, modifié il y a 9 années.]

I solved ssl connectivity problems I had a dought is CAS integrated or not

case 1: If i try to login using liferay credential in CAS (ex:-Net ID: [e-mail] Password: 123456) this shows following msg as shown in case 1 image

case 2 if i try to login using email id for both Net ID and password. The CAS is allowing to liferay portal, is correct way integrating CAS.

Regards
Ravi

[Antoine Comble, modifié il y a 9 années.]

Hi Ravi,

You can check in deployerConfigContext.xml CAS file, what authentication manger is used.
By default in CAS, the authenticationManager is DefaultAuthenticationManager and to succeed your login, you should enter username=password.

According to the scenario you described, i think you're using the DefaultAuthenticationManager.

Regards,

Antoine

[RAVI RAJAMANI, modifié il y a 9 années.]

Hi Antoine Comble,


Ya right , I am using the DefaultAuthenticationManager. but how to do login using the liferay username and password i.e instead of default authentication. please help me how to do this


Regards
Ravi R

[Antoine Comble, modifié il y a 9 années.]

To achieve this, you can below these instructions :
- Download cas-server-webapp from Jasig CAS web site
- Create your own LiferayPasswordEncoder.class based on your Liferay portal password encryption method (sha, md5, ...) : this class msut implement PasswordEncoder
- Edit the deployerConfigContext.xml file, like this : (replace all [[XXX]] by your own values)

<!--?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" 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.0.xsd
       http://www.springframework.org/schema/security http://www.springframework.org/schema/security/spring-security-3.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" />
				<!--
					| 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.adaptors.jdbc.SearchModeSearchDatabaseAuthenticationHandler">
                                <property name="tableUsers">
                                        <value>User_</value>
                                </property>
                                <property name="fieldUser">
                                        <value>screenName</value>
                                </property>
                                <property name="fieldPassword">
                                        <value>password_</value>
                                </property>
                                <property name="passwordEncoder">
                                        <bean class="[[YOUR LIFERAY PASSWORD ENCODER.class]]">
                                                <!-- Default Liferay Password Encryption is SHA algorithm. If someone changes it in liferay it have to been changed here-->
                                                <constructor-arg name="encodingAlgorithm" value="[[YOUR ALGORITHM]]"></constructor-arg>
                                        </bean>
                                </property>
                                <property name="dataSource" ref="dataSource"></property>
                        </bean>
			</list>
		</property>
	</bean>

	<!-- Data source definition point to Liferay database -->
    <bean id="dataSource" class="org.apache.commons.dbcp.BasicDataSource">
        <property name="driverClassName">
            <value>com.microsoft.sqlserver.jdbc.SQLServerDriver</value>
        </property>
        <property name="url">
            <value>[[YOUR DATABASE URL]]</value>
        </property>
        <property name="username">
            <value>[[YOUR DATABASE USERNAME]]</value>
        </property>
        <property name="password">
            <value>[[YOUR DATABASE PASSWORD]]</value>
        </property>
        <property name="initialSize" value="1"></property>
        <property name="maxIdle" value="5"></property>
        <property name="maxActive" value="50"></property>
        <property name="maxWait" value="10000"></property>
        <property name="validationQuery" value="select 1"></property>
        <property name="testOnBorrow" value="false"></property>
        <property name="testWhileIdle" value="true"></property>
        <property name="timeBetweenEvictionRunsMillis" value="10000"></property>
        <property name="minEvictableIdleTimeMillis" value="30000"></property>
        <property name="numTestsPerEvictionRun" value="-1"></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 Spring Security to find it.
	 -->
    <!-- <sec:user name="@@THIS SHOULD BE REPLACED@@" password="notused" authorities="ROLE_ADMIN" />-->

    <sec:user-service id="userDetailsService">
        <sec:user name="@@THIS SHOULD BE REPLACED@@" password="notused" authorities="ROLE_ADMIN" />
    </sec:user-service>
	
	<!-- 
	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">
            <property name="registeredServices">
                <list>
                    <bean class="org.jasig.cas.services.RegexRegisteredService">
                        <property name="id" value="0" />
                        <property name="name" value="HTTP and IMAP" />
                        <property name="description" value="Allows HTTP(S) and IMAP(S) protocols" />
                        <property name="serviceId" value="^(https?|imaps?)://.*" />
                        <property name="evaluationOrder" value="10000001" />
                    </bean>
                    <!--
                    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 example.com" />
                        <property name="description" value="Allows HTTP(S) and IMAP(S) protocols on example.com" />
                        <property name="serviceId" value="^(https?|imaps?)://([A-Za-z0-9_-]+\.)*example\.com/.*" />
                        <property name="evaluationOrder" value="0" />
                    </bean>
                    -->
                </list>
            </property>
        </bean>

    <bean id="auditTrailManager" class="com.github.inspektr.audit.support.Slf4jLoggingAuditTrailManager" />
</beans>
[code]
- Build the war
- Deploy it
- You should log in into Liferay using screenname and password or email and password (depends on your Liferay setup)

Hope this help you,

Antoine