Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
srm-client: support srm operations with bearer token
Motivation: The common srm-client now supports non-X.509 bearer token. The command-line client should be updated to take advantage of this new feature. NB. file transfers are NOT adjusted by this patch. By default, gsiftp is used, which requires X.509 authentication. Therefore transfers (srmcp) will fail with OpenID-Connect authentication. Modification: Update configation to make X.509 client authentication optional. Update wrapper script so that the auto-detected X.509 is only done if no bearer_token argument is supplied. The user can supply a bearer token on the command-line, which srm-client will use in the Authorization HTTP request header. Result: The SRM command-line clients now support bearer token authentication in addition to supporting X.509 authentication. NOTE SRM transfers with bearer token are not yet supported. Target: master Requires-notes: yes (srm-client) Requires-book: yes Patch: https://rb.dcache.org/r/12568/ Acked-by: Dmitry Litvintsev
- Loading branch information
1 parent
c39689b
commit 73a7a7c
Showing
8 changed files
with
104 additions
and
32 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters