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
Next: Root
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.
I'm currently evaluating Crowd and there is one specific functionality that I need - I would like to setup an event listener that will get called during an authentication (from ANY application as setup in Crowd) and use the corresponding username and password for further processing. I noticed there is an event in Crowd called UserAthenticationSuceededEvent (http://docs.atlassian.com/atlassian-crowd/latest/com/atlassian/crowd/event/user/UserAuthenticationSucceededEvent.html) but it does not seem to provide the username and password. Any advice is appreciated.
Thank you.
Thanks for your quick reply. Unfortunately, the product that I am trying to integrate does not support (Crowd) SSO out-of-the-box and I have no access to its source code (a third-party product). It does provide a REST API for authentication but requires both the username and password. The only workaround that I could think of is to have Crowd authenticates behalf of the user when the user authenticate via crowd, which at that point I could forward both the username and password into the product for authentication behalf of the user. However, this requires Crowd to provide both username and password via its event. I'm running out of idea, any suggestions?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Since the event is fired after the authentication is done, it will just return the token to let the client to keep login with the applicaiton. But it will at least return the user. Having password insde should be less secure, isn't it?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for your quick reply. Unfortunately, the product that I am trying to integrate does not support (Crowd) SSO out-of-the-box and I have no access to its source code (a third-party product). It does provide a REST API for authentication but requires both the username and password. The only workaround that I could think of is to have Crowd authenticates behalf of the user when the user authenticate via crowd, which at that point I could forward both the username and password into the product for authentication behalf of the user. However, this requires Crowd to provide both username and password via its event. I'm running out of idea, any suggestions?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.