Support for service principal authentication about cloud-integration-beta HOT 5 CLOSED

Thanks for raising this @karolz-ms! I've added it to our backlog.

from cloud-integration-beta.

Thanks for the proposal. Actually we looked at Service provider login for our CI as well.
One issue I see at the moment for providing this to users is that login through this method, I get an access token (valid for 1h) but no refresh token. So unlike the classic login, where the token is refreshed automatically, here the user has a token valid for 1h, and then gets an error message saying he needs to login again.
Maybe I missed something when implementing this, we can investigate a bit more to defined what is the best solution to improve this, or if we are happy to provide this in the CLI knowing the token will expire and not automatically refresh in this case. (cc @nebuk89)

from cloud-integration-beta.

Discussing this a bit further with @nebuk89, we'll include this in the CLI with the limitation that Service Principal login will obtain only an access token and no refresh token, the user will need to manually re-login when the token expires. This should not be an issue for CI use cases.
the CLI will provide: docker login azure --client-id xxx --client-secret yyy --tenant-id zzz

from cloud-integration-beta.

Makes sense, thanks Guillaume! I found this doc, which suggests that client credentials flow can only produce an access token, and not a refresh token https://docs.microsoft.com/en-us/azure/active-directory/develop/security-tokens#how-each-flow-emits-tokens-and-codes

Like you said, this is sufficient for CI scenario

from cloud-integration-beta.

Available since v0.1.12, using docker login azure --client-id xx --client-secret yy --tenant-id zz

from cloud-integration-beta.