You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
After reading the following documentation to integrate crowd and spring https://confluence.atlassian.com/display/CROWD/Integrating+Crowd+with+Spring+Security, I still have some questions.
My goal is to implement SSO for our own custom application and Jira, Confluence.
1)First of all I have a problem with the authentication provider:
Initially, to authenticate the users when connecting to our application, I use the class DaoAuthenticationProvider from spring like this:
<beans:bean id="daoAuthenticationProvider" class="org.springframework.security.authentication.dao.DaoAuthenticationProvider">
<beans:property name="userDetailsService" ref="userDetailsService/">
<beans:property name="saltSource" ref="saltSource/">
<beans:property name="passwordEncoder" ref="passwordEncoder/">
but Crowds uses a different provider(RemoteCrowdAuthenticationProvider) which expects different parameters.
How can I deal with these 2 providers?
2)The documentation says:If you have an existing user data model, then you can extend or wrap the CrowdDetailsService does it mean my model must extend the CrowdUserDetailsServiceImpl class?
Having looked at the document you are referring to, it is is suggesting that extending the CrowdUserDetailsServiceImpl class in your own application should allow you to get this configured.
All the best,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.