OSASINFRA-3756: Add support for token-based authentication in clouds.yaml configuration file #1221
Conversation
|
@dkokkino: This pull request references OSASINFRA-3756 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.20.0" version, but no target version was set. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
openshift-ci-robot
added
the
jira/valid-reference
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: dkokkino The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Previously, authentication with Swift supported application credentials, username/password or the legacy ApiKey. This commit adds support for authenticating using Keystone tokens via the token-based authentication method.
|
/retest |
|
@dkokkino: all tests passed! Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
Previously, authentication with Swift supported application credentials, username/password or the legacy ApiKey. This commit adds support for authenticating using Keystone v3token.