Known Issue: Agentforce for Developers Can Experience Access Issues when Multi-Factor Authentication enabled in an Org

[klewis-sfdc]

Summary

• When multi-factor authentication is enabled in an Org, it can sometimes interfere with the extension's ability to connect to the Org, resulting in a status of "No Agentforce for Developers Permission in Default Org"
  • Note: this does not occur for every org with MFA enabled. The A4D team has tested authenticating via the MFA webflow and had success. However, there are some orgs where the configuration of MFA interferes with the authentication process, and A4D is left in a state where it is unable to connect to the org to verify that A4D is enabled.

When this scenario occurs this is the resulting UI with Dev Assistant open:

If an org is experiencing this issue, the current resolution is to either disable MFA or switch to a different org.

Steps To Reproduce:

This issues is reproducible among some orgs with MFA enabled, and not reproducible in some orgs that have MFA enabled.

Expected result

• after authenticating via webflow and getting a refresh token, A4D should work for authenticated users.

Actual result

• Dev Assistant shows as being unable to access A4D, status menu reports No Permission

Additional information

Salesforce Extension Version in VS Code: 62.9.1

Salesforce Einstein For Developers Version in VS Code: 1.6.0

OS and version: Sonoma 14.7.1

VS Code version: 1.96.0

[fabmeyer]

When will this be fixed?

[gbockus-sf]

Hi @fabmeyer
I followed up on the internal issue with had with the auth team and it was marked Working as designed (not ideal). I'll create a WI for this issue so the A4D team can follow up on it and ensure we get it figured out.

[git2gus]

This issue has been linked to a new work item: W-17647165

[diyer]

@fabmeyer can you provide the org Id and instance id that is having this issue?
Also what type of org is this? sandbox/scratch/prod?