question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Unable to sign into Bot Framework Composer - No Azure Directories were found

See original GitHub issue

Describe the bug

I’ve got an Azure instance. Have successfully signed into Bot Emulator & Azure cli but cannot sign into Bot Composer at all - just get the error message “No Azure Directories were found”

Interestingly after I put in my e-mail address it is not asking me for a password, it just errors out.

Version

Version: 2.1.2 Electron: 8.2.4 Chrome: 80.0.3987.165 NodeJS: 12.13.0 V8: 8.0.426.27-electron.0

Browser

  • Electron distribution
  • [x ] Chrome
  • Safari
  • Firefox
  • Edge

OS

  • macOS
  • [ x] Windows
  • Ubuntu

To Reproduce

Additional context

Found another post here which suggested getting the console log. The relevant bit of the console log is pasted below:

2022-02-22T15:17:44.454Z composer:electron:app-updater Resetting to idle… POST /api/assets/projectTemplates 200 1219.000 ms - - POST /api/telemetry/events 200 2.200 ms - 2 2022-02-22T15:18:25.141Z composer:electron:one-auth PII logging enabled: false 2022-02-22T15:18:25.142Z composer:electron:one-auth Attempting to load oneauth module from C:\Users*****\AppData\Local\Programs\Bot Framework Composer\resources\app.asar.unpacked\oneauth. 2022-02-22T15:18:25.151Z composer:electron:one-auth Initializing… 2022-02-22T15:18:25.154Z composer:electron:one-auth Service initialized. 2022-02-22T15:18:25.154Z composer:electron:one-auth Logging user into ARM… [OneAuth:Warning:9a8hm:e993a05e-b8e0-41ca-8c3f-9a5aefa91694] HTTP status: 403 [OneAuth:Warning:9a8hm:e993a05e-b8e0-41ca-8c3f-9a5aefa91694] HTTP status: 403 2022-02-22T15:18:26.168Z composer:electron:one-auth 3 [OneAuth:Warning:9a8hm:e993a05e-b8e0-41ca-8c3f-9a5aefa91694] HTTP status: 403 [OneAuth:Error:835v1:e993a05e-b8e0-41ca-8c3f-9a5aefa91694] (Code:2001) The resource is forbidden. [OneAuth:Error:835v1:e993a05e-b8e0-41ca-8c3f-9a5aefa91694] (Code:2001) The resource is forbidden. [OneAuth:Warning:96w1t:e993a05e-b8e0-41ca-8c3f-9a5aefa91694] Failed to get profile image from Graph [OneAuth:Warning:96w1t:e993a05e-b8e0-41ca-8c3f-9a5aefa91694] Failed to get profile image from Graph 2022-02-22T15:18:26.169Z composer:electron:one-auth 2 [OneAuth:Error:835v1:e993a05e-b8e0-41ca-8c3f-9a5aefa91694] (Code:2001) The resource is forbidden. 2022-02-22T15:18:26.169Z composer:electron:one-auth 3 [OneAuth:Warning:96w1t:e993a05e-b8e0-41ca-8c3f-9a5aefa91694] Failed to get profile image from Graph 2022-02-22T15:18:33.891Z composer:electron:one-auth 3 [MSAL:0009] WARNING TryReadUniversalStorage:343 Attempted to read cache with a non-normalized realm, access token and ID token reads will fail 2022-02-22T15:18:33.894Z composer:electron:one-auth 3 [MSAL:0009] WARNING TryReadUniversalStorage:447 No id token found in the cache 2022-02-22T15:18:33.895Z composer:electron:one-auth 3 [MSAL:0009] WARNING TryReadUniversalStorage:463 No access token found in the cache [OneAuth:Warning:9a8hm:70049068-65f5-42e0-acbe-c7404bb4497f] HTTP status: 403 [OneAuth:Warning:9a8hm:70049068-65f5-42e0-acbe-c7404bb4497f] HTTP status: 403 [OneAuth:Error:835v1:70049068-65f5-42e0-acbe-c7404bb4497f] (Code:2001) The resource is fo``` rbidden.2022-02-22T15:18:34.290Z composer:electron:one-auth 3 [OneAuth:Warning:9a8hm:70049068-65f5-42e0-acbe-c7404bb4497f] HTTP status: 403

[OneAuth:Error:835v1:70049068-65f5-42e0-acbe-c7404bb4497f] (Code:2001) The resource is forbidden. [OneAuth:Warning:96w1t:70049068-65f5-42e0-acbe-c7404bb4497f] Failed to get profile image from Graph2022-02-22T15:18:34.293Z composer:electron:one-auth 2 [OneAuth:Error:835v1:70049068-65f5-42e0-acbe-c7404bb4497f] (Code:2001) The resource is forbidden.

[OneAuth:Warning:96w1t:70049068-65f5-42e0-acbe-c7404bb4497f] Failed to get profile image from Graph 2022-02-22T15:18:34.295Z composer:electron:one-auth 3 [OneAuth:Warning:96w1t:70049068-65f5-42e0-acbe-c7404bb4497f] Failed to get profile image from Graph 2022-02-22T15:18:34.389Z composer:electron:one-auth There was an error trying to log the user into ARM: FetchError: request to https://management.azure.com/tenants?api-version=2020-01-01 failed, reason: self signed certificate in certificate chain at ClientRequest.<anonymous> (C:\Users*****\AppData\Local\Programs\Bot Framework Composer\resources\app.asar\node_modules\node-fetch\lib\index.js:1461:11) at ClientRequest.emit (events.js:210:5) at TLSSocket.socketErrorListener (_http_client.js:406:9) at TLSSocket.emit (events.js:210:5) at emitErrorNT (internal/streams/destroy.js:92:8) at emitErrorAndCloseNT (internal/streams/destroy.js:60:3) at processTicksAndRejections (internal/process/task_queues.js:80:21) { message: ‘request to https://management.azure.com/tenants?api-version=2020-01-01 failed, reason: self signed certificate in certificate chain’, type: ‘system’, errno: ‘SELF_SIGNED_CERT_IN_CHAIN’, code: ‘SELF_SIGNED_CERT_IN_CHAIN’ } GET /api/auth/getTenants 500 9249.074 ms - 232


Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:8

github_iconTop GitHub Comments

1reaction
nickfranciscommented, Feb 28, 2022

Resolved - it was Netskope running on local machine - need to find a work around within the company tenant…

0reactions
nickfranciscommented, Aug 5, 2022

Yes - had to disable Netskope services on my machine before I could connect to Composer. Once disabled all works as it should.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Azure sign-in Sign in failed: No Azure Directories were found.
Login in with my credentials Im always receiving the following error: Azure sign-in Sign in failed: No Azure Directories were found.
Read more >
No Azure Directories were found error in Bot Framework ...
Running into this error when trying to publish through Bot FW Composer. I have to log in through Composer to do this, but...
Read more >
No Azure Directories were found error in Bot Composer
Running into this error when trying to publish through Bot FW Composer. I have to log in through Composer to do this, but...
Read more >
Add authentication to a bot in Bot Framework SDK - Bot Service
Your bot doesn't need to manage authentication tokens because Azure does it for you using OAuth 2.0 to generate a token based on...
Read more >
Sign in to your Azure account in Bot Framework Composer
Select the user icon in the upper right. In the drop-down menu, select Sign in to your Azure account. Composer Azure sign in....
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found