Describe the bug
Currently, cybr-cli uses platform discovery to determine the tenant id. It then uses the format of tenantid.id.cyberark.cloud to start authentication with Identity. In some instances, a PodFqdn could be required instead of utilizing the tenant id. If this is the case, that is the only value returned in the JSON response when starting authentication. This is not currently supported in cybr-cli.
To Reproduce
Steps to reproduce the behavior:
Setup a PodFqdn for your Identity tenant.
Attempt a cybr logon command using -a identity.
Expected behavior
Regardless of whether a PodFqdn is required or not, cybr-cli should be able to determine the proper base URL to send the start authentication request to.
Describe the bug Currently, cybr-cli uses platform discovery to determine the tenant id. It then uses the format of
tenantid.id.cyberark.cloud
to start authentication with Identity. In some instances, a PodFqdn could be required instead of utilizing the tenant id. If this is the case, that is the only value returned in the JSON response when starting authentication. This is not currently supported in cybr-cli.To Reproduce Steps to reproduce the behavior:
cybr logon
command using-a identity
.Expected behavior Regardless of whether a PodFqdn is required or not, cybr-cli should be able to determine the proper base URL to send the start authentication request to.