-
Notifications
You must be signed in to change notification settings - Fork 33
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
Support for Encrypted Authorization Token #107
Comments
Hi,
Regards, |
Hello Prasad Thanks for your reply. On our environment we enforce the use of named users for auditing purposes. We need the traceability. I don't think that storing the switch password on our servers is not safe. We can put it in the Ansible Vault but in that case we have to decrypt the vault when running a playbook. The password for the vault can also be stored in a file but this is also not very secure. Kind regards |
Hi Bert, |
Hi Bert, |
Hello
I would like to use the encrypted authorization tokens for our environment.
I see in the file below that Basic authorization is used and that there is no possibility for 'Custom_Auth'.
Is this on the roadmap?
utils/brocade_connection.py
credential = {"Authorization": "Basic " + login_encoded.decode(), "User-Agent": "Rest-Conf"}
The text was updated successfully, but these errors were encountered: