[jboss-user] [Security & JAAS/JBoss] - Re: Deploying issue with SSO

[sohil.shah@jboss.com]

Nipun-

If you are using jboss 4.0.3 then you dont need to patch your tomcat.sar file with the tomcat-util.jar file. Its only for cookie processing issues in tomcat.sar in jboss-4.0.4 and jboss-4.0.5


As far as your ClassCastException goes, just remove the 


  | <provisioning>
  | 			<provider id="si:jboss-sso:ldap:provisioning" class="org.jboss.security.idm.ldap.LDAPIdentityProvider">
  | 				<property name="connectionURL">
  | 					jdbc:ldap://localhost:389/dc=jboss,dc=com?SEARCH_SCOPE:=subTreeScope&amp;secure:=false&amp;concat_atts:=true&amp;size_limit:=10000000
  | 				</property>
  | 				<property name="username">cn=Admin,dc=jboss,dc=com</property>
  | 				<property name="password">jbossrocks</property>
  | 				<property name="identityOu">jbosssso</property>
  | 				<property name="roleOu">role</property>
  | 			</provider>
  | 		</provisioning>
  | 
  |   | 
  |   | configuration from the jboss-sso.sar/conf/sso.cfg.xml file.
  |   | 
  |   | You only need to specify the login provider, not the provisioning provider at this point.
  |   | 
  |   | ProvisioningProvider will be important for Federated Provisioning functions that are on the roadmap.
  |   | 
  |   | Thanks
  |   | Sohil

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3982487#3982487

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3982487