Issue while connecting "twice"

[lukedaemon]

Hello,
I’m connecting to a Dynamics 365 environment with the following:

$myConn = Connect-CrmOnline -ServerUrl <ServerUrl> -Username user1@domain.com
# Auth window appears → sign in succeeds
Get-CrmRecords -Conn $myConn ...

This works as expected. However, in the same PowerShell session if I connect with a different account:

$myConn = Connect-CrmOnline -ServerUrl <ServerUrl> -Username user2@domain.com
# Auth window appears → sign in succeeds

Every subsequent Get-CrmRecords -Conn $myConn ... triggers the OAuth prompt again.
The only way I’ve found to stop the repeated prompts is to close the PowerShell session and start a new one.

Any thoughts ?

[seanmcne]

I'd suggest trying the connection command which forces oAuth, it's possible this matters to how it stores or caches the tokens for example:

$prodConn = Connect-CrmOnline -ServerUrl -ForceOAuth

$devConn = Connect-CrmOnline -ServerUrl -ForceOAuth

I know this was an issue in an earlier release of XRM Tooling Connector (a long while back) but I recall getting it working again in a later release (for scenarios where the user wants to connect to two environments to compare information, or for other scenarios).

I used the above connection commands with two different variable names and when I look at this (after connecting to both) I see they're both pointed at different environments and when I execute a whoAmI I also see the specific information for my user for each of those environments:

Invoke-CrmWhoAmI -conn $devConn

Invoke-CrmWhoAmI -conn $prodConn

[lukedaemon]

Hello,
If I specify the ForceOAuth parameter for the Connect-CrmOnline cmdlet, the OAuth window briefly appears and then disappears (so I don’t get the chance to enter credentials). I assume it’s using the currently cached identity. I can confirm this from the cmdlet output (specifically the OAuthUserId property).

Connect-CrmOnline -ServerUrl -ForceOAuth

The same happens if I also provide the Username parameter: the authentication window pops up and immediately closes, and in addition to the cmdlet output, the following error appears:

Connect-CrmOnline -ServerUrl -Username -ForceOAuth

Connect-CrmOnline : Warning: Exception encountered when authenticating, if you're using oAuth you might want to include the -username paramter to disambiguate the identity used for authenticate

[seanmcne]

Interesting - one thing you can try for more info is to add the -verbose parameter, it should at least give you the connection string and some additional debug info to help reproduce w/ crmserviceclient or you can use something like XRM Toolbox to help diagnose if the same connection string works there or not.

connect-crmonline -ServerUrl https://environment.crm.dynamics.com -verbose -forceoAuth

I would expect to see similar behavior from any other app that uses crmServiceClient.