Hey folks!
I'm implementing a custom SSO solution for FishEye/Crucible, and I've only got one snag keeping it from perfection. I've written an authenticator that extends AbstractFishEyeAuthenticator, and plugged the proper authentication login into the checkPassword and checkRequest methods. I can authenticate, and existing authentication cookies from other apps are logging me in correctly.
Only problem is getting my FishEye login to persist to other applications. All I need is to create a cookie containing the SSO session ID after authentication, but I'm not sure that's possible... The checkPassword method is called during authentication, so it'd be a perfect place to create cookies. Problem is, it doesn't have any knowledge of the Request or Response objects. I wish this method took more than just username and password as parameters...
Does anyone know if this is even possible, given FishEye's architecture? I'd hate for this to be the only thing keeping me from true SSO across all our applications.
Thanks!
- Michael
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.