[BUG] Authentication for this request failed. error for accessing non-US environments about cds-for-code

[CloudSmithBrandon]

Hi @LinnZawWin and others,

Given the severity of this issue, we've gone ahead and pushed the fix (and a related set of fixes) to the 0.8.12 release on the VSCode Marketplace. Please update your extension to this version (Extension > CDS for Code > Update) and attempt to re-connect.

If you had already saved this connection, it may be necessary to remove and re-add the connection. We apologize for the inconvenience. Please let us know if you continue to experience issues.

[CloudSmithIra]

Thank you for your detailed bug report. We have this on the backlog now and will begin diagnosis this sprint.

[CloudSmithBrandon]

Hello,

We've been investigating this issue and have not yet been able to correlate it with telemetry tracking login failures. If you could provide us with a little more information, it should help us determine the cause of this issue:

1. When you re-start VSCode, are you able to successfully expand the node for the .crm6.dynamics.com instance? (This will let us know if it's an issue with the local state of the view or not)
2. Does the account you're using to register your .crm6.dynamics.com connection use MFA (multi-factor authentication)?
3. What is your OS/VSCode version?

We will attempt to reproduce this issue internally and update shortly.

Thanks,
Brandon

[LinnZawWin]

1. When I re-start VSCode, I am not even able to expand the first connection node. (previously, I was able to expand the node for the connection but not for the environment (2nd) node)
   

2. The account I'm using to register my .crm6.dynamics.com connection does not use MFA (multi-factor authentication)

3. OS version: Windows 10 Version 1909 Build 18363.592
   VSCode version: 1.42.0

[CloudSmithBrandon]

Thank you, this is helpful. We're very sorry you've been having this experience. This is certainly an odd behavior that we haven't seen before. Here's how I'd like to proceed.

1. We will build a repro of this scenario using a trial tenant in Aus/NZ (crm6.dynamics.com)
2. If we can repro, then we'll update this with the status of a fix.
3. If we can't, and if you're willing, I'd like to have you run a debug build of the extension using screen sharing so that we can evaluate this scenario with you interactively. My team and/or I would be happy to setup a time to work with you in your local time zone (NZ). Given the time difference (we are Eastern US time zone), this would likely be earlier in your day.

I will update the status of this issue today with our findings from the repo using the trial tenant in your Geo.

[LinnZawWin]

Sounds like a plan. I'm happy to run a debug build of the extension using screen sharing.

[CloudSmithBrandon]

Hi @LinnZawWin ,

We were able to reproduce this issue using a trial tenant in the APAC region (specifically, we requested the tenant in New Zealand). This does appear to be localized to the region, and we apologize for the trouble.

My team and I are working on a fix that will drop with the 0.9.0 build. After the fix is ready, I can share a private build with you to evaluate/verify the fix works in your scenario, or we can share instructions on how to download and build/run the fix from GitHub. Please email [email protected] and reference GitHub Issue #10 and a link to the build will be emailed back to you when it is ready.

Thank you for offering the time to work with us on a repro. At this point, since we are able to reproduce this issue in-house, I do not believe it will be necessary to schedule a screen sharing session.

Regards,
Brandon