-
Notifications
You must be signed in to change notification settings - Fork 23.7k
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
Update guide_azure.rst #54401
Update guide_azure.rst #54401
Conversation
Added a note to the 'Storing in a file' section, that the secret value of the ini file should be UrlEncoded. Otherwise the user might get login errors (depends on the characters used in the secret). +label: docsite_pr
@yuwzho would it be correct to say |
@acozine Actually I am thinking about handling this in code level. It doesn't make sense from user's perspective to do the encoding in no matter .ini file or environment variable, right? |
@yuwzho handling this in the code seems like a smart approach - then users don't need to worry about encoding. What's the timeframe on changing the code? It might make sense to merge this docs PR now if the code fix is going to take days or weeks. |
The test
The test
|
I am a bit busy these time, would you like to propose a change? The code snippet should be at these lines around @acozine ansible/lib/ansible/module_utils/azure_rm_common.py Lines 1076 to 1080 in 08c7dd9
|
@yuwzho I'm a docs person, not a developer, so I'll leave the code changes for someone else to do. Once this PR passes Shippable, I'm going to merge it, then open an issue for the code change. |
+label: docsite_pr
SUMMARY
Added a note to the 'Storing in a file' section, that the secret value of the ini file should be UrlEncoded.
Otherwise the user might get login errors (depends on the characters used in the secret).
ISSUE TYPE
COMPONENT NAME
guide_azure.rst
ADDITIONAL INFORMATION
If the secret of the azure service principal contains unusual characters, the login will fail.
The secret must be urlencoded() to avoid this login error.
See also this discussion, wich got me to the solution:
https://stackoverflow.com/questions/42477266/aadsts50012-invalid-client-secret-is-provided-when-moving-from-a-test-app-to-pr