Hi All!!!,
Iam working on enabling federated SSO for Jive SBS 3.0.6 with crowd as an identity management provider. I followed the article -
http://www.jivesoftware.com/jivespace/docs/DOC-3277 & http://www.jivesoftware.com/jivespace/docs/DOC-3279
I managed to authenticate the user from crowd and fulfilled the authentication contract. But after succefully processsing the filter chain jive tries to forward the request to cs_login page, which couldn't be found. No exception/errors were logged in log files.
And when I hit the Jive landing page url in same window the user is shown as logged in. Why jive is directing to cs_login instead of index.jspa ? What else I do to make it working ?
Regards,
Ashish
Hi Ashish,
I am not exactly sure what could be going wrong. Do you mind attaching the source code of your plugin to this thread?
Thanks,
Cory
Hi Cory,
Attached is the source code of my custom filter. I have also changed spring-securityContext.xml file for FilterChainProxy -
/**=httpSessionContextIntegrationFilter, federatedIdentityAuthFilter, sessionTrackingFilter, loginPopupFormAuthenticationFilter, rememberMeProcessingFilter, feedBasicAuthenticationFilter,exceptionTranslationFilter,jiveAuthenticationTranslationFilter,contextOptimizationFilter,myTestFilter
I have added myTestFilter at the end just to check whether SecurityContext holds a valid JiveUserAuthentication or not, in other words custom filter conforms to authentication contract.
And I observed that the authenticated user detail are accessible in myTestFilter via SecurityContext.
Regards,
Ashish
Hi Cory,
Did you find any thing wrong in the filter? Please share updates if you have any.
Regards,
Ashish
Even if I remove myTestFilter, it won't work.
Jive combines collaboration software, community software & social networking software into the leading SBS solution.
© Copyright 2000–2009 Jive Software. All rights reserved.
915 SW Stark St., Suite 400, Portland, OR 97205