auth:renew should respect set alternative AccountManager url
See original GitHub issueCurrently, auth:renew
calls obtainToken
with no AccountManager override. So when one was initially set, renew
will try to re-authenticate with the standard AccountManager.
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
No results found
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I think respecting the alternative Account Manager host passed to
sfcc-ci client:auth
via-a
flag, is not trivial. The setting is only visible to the current Node process running the command, this includes playing withprocess.env.SFCC_LOGIN_URL
and setting the host. One option would be to persist the setting into the CLIs local configuration. That however, has the downside that it would be visible across shells and sessions.I’d personally favor to deprecate the flag
-a
for commandsfcc-ci client:auth
and rely on env varSFCC_LOGIN_URL
.I’ve created #129 for the removal of flag
-a,--authserver
and closing this one.