-
Notifications
You must be signed in to change notification settings - Fork 4
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
Unable to connect to Rally sandbox environment using security token #18
Comments
Closed the issue accidentally |
Adding more test results - In Sandbox environment, a GET request is made which gets the security token in the response body. In the subsequent API calls, this security token is passed as a parameter "key". REST API call to Sandbox Rally using Postman:
Subsequest REST API call -
Rest API call to Production Rally using Postman:
Please let me know if you have any questions. |
Hello again @vishnukadi . Thanks for your issues with tons of details - you really make our work so much easier! @wasabibob and I will take a crack at this |
@vlussenburg and @wasabibob |
@vishnukadi please be aware that your BASIC AUTH hash was in the HTTP output above (I cut it out) so you probably want to reset the password for the |
@vlussenburg my bad, I missed to clip it out. I'll get it reset, thank you for letting me know, |
hi @vishnukadi the pyral library should handle security token authentication automatically. I was able to log in to my test instance of rally with only username and password, leaving the token field blank. Please see this link for additional information on how pyral handles security tokens. Can you try to run the check connection task with only username and password? |
To verify this fact, I added additional logging to my
|
Hi @jpflug , thanks for your input.
|
Hello @vishnukadi I am sorry to hear that. I was able to successfully connect to my rally test instance using https via XL Release. The error you receive is from the underlying pyral library which the XLR plugin utilizes to complete rally activities. Are you able to install pyral locally to directly test connection and endpoints outside XL Release? I saw some cases where the pyral logging was being suppressed by XLR so it will be essential to remove the additional complication of XLR to determine the root cause here. |
Test connection to Rally sandbox is unsuccessful using username, password and security token
Sandbox url: sandbox.rallydev.com
API keys are not supported in the Sandbox environment. In order to connect to Sandbox environment, a security token must be used.
Generated security token by logging in to https://sandbox.rallydev.com/slm/webservice/v2.0/security/authorize using Rally service account credentials.
Copied the security token and pasted it in OAuth Key field
Title: Rally
Url: sandbox.rallydev.com
Authentication Method: Basic
Username: username
Password: **********
Oauth key:
Error:
pyral.context.RallyRESTAPIError: Invalid credentials
Since API keys are not supported in the Sandbox environment, we would need the plugin configured to accept security token as well.
The text was updated successfully, but these errors were encountered: