Device code authentication support

[Hazellie]

I might be wrong, but as Dataverse is built on top of regular MSAL, it should be possible to implement device code authentication? I can only think of Dataverse not directly (to my knowledge) supporting it which might require a token exchange and I'm not sure how nice that would play with everything.

The use case is also a bit niche, but the regular PAC CLI supports it and I make use of it heavily since I SSH into my development environment often, having to switch to the physical machine just for the authentication step is tedious to say the least.

[neronotte]

I'm not an expert on Device Code Authentication but... PACX relies on Microsoft.PowerPlatform.Dataverse.Client library, thus it supports all the auth schemes valid for that library.

You should be able to create a connection string like the following one:

AuthType=OAuth;
Url={DataverseUrl};
AppId={ClientId};
RedirectUri=urn: ietf:wg:oauth:2.0:oob;
LoginPrompt=Always;

Connection String Parameters Explained

• AuthType=OAuth: Specifies OAuth authentication
• Url: Your Dataverse environment URL
• AppId: Your Azure AD application (client) ID
• RedirectUri=urn:ietf:wg:oauth:2.0:oob: Standard redirect URI for device code flow
• LoginPrompt=Always: Forces the authentication prompt every time

Let me know if it works, I'm curious

[neronotte]

No answer provided. I'm closing this for obsolescence