Comment 11 for bug 1680523

Try again now. http://lastcoolnameleft.com/mini/azure.log
(might need a hard refresh of the page)

On Mon, Apr 10, 2017 at 10:45 PM Anastasia <email address hidden>
wrote:

> Removing Juju milestone to avoid confusion :D
>
> ** Changed in: juju
> Milestone: 2.2-beta3 => None
>
> ** Changed in: juju
> Status: Fix Committed => Fix Released
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1680523
>
> Title:
> add-credential azure fails
>
> Status in juju:
> Fix Released
>
> Bug description:
> I am receiving the following error when running "juju add-credential
> azure". I have tried two different subscription ID's, both have the
> same issue.
>
> Sign In
> Sorry, but we’re having trouble signing you in.
> We received a bad request.
>
> Additional technical information:
> Correlation ID: 9da27091-d4a3-4e93-81e0-41e016d8276a
> Timestamp: 2017-04-06 16:01:06Z
> AADSTS90093: Calling principal cannot consent due to lack of permissions.
>
> To reproduce the problem:
>
> ➜ ~ juju add-credential azure
> Enter credential name: test
> A credential with that name already exists.
>
> Replace the existing credential? (y/N): y
> Auth Types
> interactive*
> service-principal-secret
>
> Select auth-type: interactive
> Enter subscription-id: <removed>
> Initiating interactive authentication.
>
> To sign in, use a web browser to open the page
> https://aka.ms/devicelogin and enter the code <removed> to
> authenticate.
>
> -- Go to link
>
> Enter the code that you received from the application on your device
>
> Juju CLI Application publisher: Click cancel if you received this code
> from a different application
>
> -- Click Continue
>
> -- Enter credentials
>
> Sorry, but we’re having trouble signing you in.
> We received a bad request
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1680523/+subscriptions
>