-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is there a way to use this toolkit with SSO login? #15
Comments
Not at the moment, but I've heard one or two requests for it. We would likely have to add a way to designate the Identity Provider url - I'll keep this open hopefully to spike it out soon. |
+1 Is there a way to work around this issue? |
Workaround - not at the moment - you can whitelist some users in an SSO sub of Rally to be okay for non sso auth. |
@larsxschneider and @benoitdion - I have a branch up for a spike on SSO. I cut a new gem: rally_api-0.9.17.pre which has prelimary SSO working for my sso user - hard for me to test for you, but wanted to see if it would work. Sorry for the edit - one more thing - in the config you pass in, you would now need to pass in |
Has this been merged to the main branch, or is this still only available in the --pre gem? |
@wvdschel - it is still in a pre gem. I'm thinking of changing the gem so that you can pass in your own code block for sso login. The main issue is that each SSO handshake is unique (depends on how your company setup your SSO provider). This means that it is very hard to make the code generic. The test (pre) support I had would work if the handshake only used HTML forms to do the handshake, but some customers do other actions in the handshake beyond form posting (eg Javascript or captcha). |
I think that would be a good idea. I tried it with my company's SSO page, but it seems to pick the wrong form (the search form instead of the login form). |
With the 1.0.x version of this gem, you can now use API keys for auth. See the Readme - hopefully the api keys would work for what you might need. |
No description provided.
The text was updated successfully, but these errors were encountered: