locked
azure stack login from CLI facing issues RRS feed

  • Question

  • 2017-01-20T15:28:52.798Z:
    { [Error: Get Token request returned http error: 404]
      stack: [Getter/Setter],
      __frame:
       { name: '__1',
         line: 50,
         file: 'C:\\Program Files (x86)\\Microsoft SDKs\\Azure\\CLI\\lib\\commands\\login.js',
         prev: undefined,
         calls: 0,
         active: false,
         offset: 66,
         col: 27 },
      rawStack: [Getter] }
    Error: Get Token request returned http error: 404
      <<< async stack >>>
      at __1 (C:\Program Files (x86)\Microsoft SDKs\Azure\CLI\lib\commands\login.js:116:28)
      <<< raw stack >>>
        at Logger.createError (C:\Program Files (x86)\Microsoft SDKs\Azure\CLI\node_modules\adal-node\lib\log.js:201:13)
        at Request._callback (C:\Program Files (x86)\Microsoft SDKs\Azure\CLI\node_modules\adal-node\lib\util.js:133:25)
        at Request.self.callback (C:\Program Files (x86)\Microsoft SDKs\Azure\CLI\node_modules\request\request.js:187:22)
        at emitTwo (events.js:87:13)
        at Request.emit (events.js:172:7)
        at Request.<anonymous> (C:\Program Files (x86)\Microsoft SDKs\Azure\CLI\node_modules\request\request.js:1044:10)
        at emitOne (events.js:77:13)
        at Request.emit (events.js:169:7)
        at IncomingMessage.<anonymous> (C:\Program Files (x86)\Microsoft SDKs\Azure\CLI\node_modules\request\request.js:965:12)
        at emitNone (events.js:72:20)

    #azure account env add AzureStack1 --resource-manager-endpoint-url "https://api.azurestack.local" --management-endpoint-url "https://api.azurestack.local/" --active-directory-endpoint-url "https://login.windows.net/****.onmicrosoft.com/" --portal-url "https://portal.azurestack.local" --gallery-endpoint-url "https://gallery.azurestack.local/" --active-directory-resource-id "https://azurestack.local-api/" --active-directory-graph-resource-id "https://graph.windows.net/"

    azure login -e AzureStack1 -u "user@****.onmicrosoft.com"

    Regards,

    Issac

    • Moved by Loydon Mendonca Saturday, January 21, 2017 11:32 AM Moving to Azure Stack
    Friday, January 20, 2017 3:38 PM

Answers

  • This is a known issue which we will be addressing in a future release.  Thank you for trying out this feature.
    Monday, February 13, 2017 7:46 PM

All replies

  • Hello Isahac,

    Would you please explain the operation above in a little more detail. Are you running this deployment on Azure Stack because it appears that way. I would be moving this thread from the Azure Networking (DNS, Traffic Manager, VPN, VNET) forums to the Stack forums to find better audience.

    Regards,

    Loydon


    • Edited by Loydon Mendonca Saturday, January 21, 2017 11:31 AM Moving to Stack
    Saturday, January 21, 2017 11:29 AM
  • Hi Isahac,

    Thank you for contacting Microsoft forums. We are pleased to answer your query.

    If you're getting certificate validation issues, disable certificate validation by running the command set NODE_TLS_REJECT_UNAUTHORIZED=0.

    For more details, see “Install and configure Azure Stack CLI”.

    I hope that the reply will assist you in getting your query addressed. In case you require further assistance, please do reply to the thread as we are always available to your queries.

     

    Regards,

    Pradeep

     

    Kindly click "Mark as Answer" on the post that helps you, this can be beneficial to other community members reading the thread and also “Vote as Helpful”.

    Sunday, January 22, 2017 2:03 PM
  • Thanks Pradeep  for the reply.

    Still its not working with set NODE_TLS_REJECT_UNAUTHORIZED=0.

    the error report says:

    2017-01-25T07:44:26.082Z:
    { [Error: Get Token request returned http error: 404]
      stack: [Getter/Setter],
      __frame:
       { name: '__1',
         line: 50,
         file: 'C:\\Program Files (x86)\\Microsoft SDKs\\Azure\\CLI\\lib\\commands\\login.js',
         prev: undefined,
         calls: 0,
         active: false,
         offset: 66,
         col: 27 },
      rawStack: [Getter] }
    Error: Get Token request returned http error: 404
      <<< async stack >>>
      at __1 (C:\Program Files (x86)\Microsoft SDKs\Azure\CLI\lib\commands\login.js:116:28)
      <<< raw stack >>>
        at Logger.createError (C:\Program Files (x86)\Microsoft SDKs\Azure\CLI\node_modules\adal-node\lib\log.js:201:13)
        at Request._callback (C:\Program Files (x86)\Microsoft SDKs\Azure\CLI\node_modules\adal-node\lib\util.js:133:25)
        at Request.self.callback (C:\Program Files (x86)\Microsoft SDKs\Azure\CLI\node_modules\request\request.js:187:22)
        at emitTwo (events.js:87:13)
        at Request.emit (events.js:172:7)
        at Request.<anonymous> (C:\Program Files (x86)\Microsoft SDKs\Azure\CLI\node_modules\request\request.js:1044:10)
        at emitOne (events.js:77:13)
        at Request.emit (events.js:169:7)
        at IncomingMessage.<anonymous> (C:\Program Files (x86)\Microsoft SDKs\Azure\CLI\node_modules\request\request.js:965:12)
        at emitNone (events.js:72:20)

    Regards,

    Issac

    Wednesday, January 25, 2017 7:46 AM
  • Hello,

    Please try running the cmd again to get verbose output, please use the -vv flag at the end to get verbose output.

    Also i see that your -active-directory-endpoint-url is "https://login.windows.net/****.onmicrosoft.com/"..this as an endpoint does not exist i believe, please try it with just https://login.windows.net and if it fails, please send verbose output.

    Thanks

    --
    Shri

    Wednesday, January 25, 2017 7:45 PM
  • This is a known issue which we will be addressing in a future release.  Thank you for trying out this feature.
    Monday, February 13, 2017 7:46 PM
  • Azure Stack TP3 has been released on March 1, 2017.

    If you are experiencing any issues with the TP2 release, please download and redeploy using the latest Azure Stack POC deployment package

    Please see the updated deployment documentation:

    https://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-run-powershell-script

    And updated Azure Stack Docs:

    https://docs.microsoft.com/en-us/azure/azure-stack/

    If you experience any issues with TP3 release, feel free to contact us.

    https://azure.microsoft.com/en-us/blog/hybrid-application-innovation-with-azure-and-azure-stack/

    Wednesday, March 1, 2017 6:40 PM