-
Notifications
You must be signed in to change notification settings - Fork 31
Closed as not planned
Labels
Description
Pelican Service:
- Client
- Plugin
- Registry
- Director
- Origin
- Cache
- Other (please give the detail)
The Pelican client error reported when the incorrect password is used to unlock an encrypted config file is unclear that it's referring to the configuration file. In addition, it doesn't suggest anything for how to reset the password (by deleting the configuration file and letting Pelican recreate it). See command below (file/path redactions in brackets mine):
$ ./pelican object put [put file] pelican://osg-htc.org/[put destination]
The OSDF client configuration is encrypted. Enter your password for the local OSDF client configuration file:
ERROR[2025-07-23T12:22:39-05:00] Failed to generate a new authorization token for this transfer: pkcs8: incorrect password
ERROR[2025-07-23T12:22:39-05:00] This transfer requires authorization to complete and no token is available
ERROR[2025-07-23T12:22:39-05:00] Failure putting [put file]: failed to get token for transfer: failed to find or generate a token as required for pelican://osg-htc.org/[put destination]: pkcs8: incorrect password
I was able to fix this without issue but am worried about other, less command-line-experienced users either:
- misunderstanding the
incorrect passworderror as being related to token generation rather than unlocking the configuration file to look for existing tokens. - not knowing where to look to delete their Pelican client config file.
It'd be great to see a more descriptive error that describes how to delete the client config file if the password needs to be reset (perhaps even by adding a reset subcommand to pelican config and suggesting that?).
Thanks!