ALM Toolkit login window won't open on latest version

[kakasnest]

As of version 5.1.11 when specifying a connection string to workspace and specifiying the model name there is no Microsoft login pop-up.

Until this version the default behaviour was to open a window to have credentials passed. Right now it uses the Microsoft Entra ID profile of the current user logged in to Windows (to my best knowledge).

Tested on 5.1.7, works like a charm.

Tried repair on 5.1.11, didn't work.

[christianwade]

Hi, thanks for raising. Yes, the latest version of the AS client libraries authenticate using SSO by default (and therefore doesn't bother showing the dialog). May be able to provide ability to opt out of this. Need to look into it ...

[Jon-Graber]

Is there a way around this? Currently if I put a workspace in and click to find a model it finds nothing. It doesn't tell me what's wrong or what it is using to login. If it's using my windows login then this tool is now unuseable for me as my production environment is under a different login.

[christianwade]

I asked the engineering team and there may be a solution but I don't have a timeline right now. In a couple months, I'll evaluate if a solution is doable as an option setting. Free to remind me if needed. Can you use the old version for now?

[kakasnest]

@christianwade is there any development/news regarding this? Thank you in advance.

[christianwade]

waiting for engineering response ...

[otykier]

FWIW, we're facing the same issue in TE2/TE3. Something in the authentication flow has been broken ever since the AS client library started using WAM, which I believe happened around v. 19.80.0. We can force the MFA account selector to appear by appending User ID=" " to the connection string, but this causes various issues (like repeated prompts) if we need to subsequently open additional connections, or even just by calling Server.CancelCommand(). Any threads you can pull to get this resolved would be greatly appreciated, @christianwade.

[KNP-BI]

Hi @otykier,

What version of TE2 would I need to revert to, to get around this issue?
Thanks.

[KNP-BI]

Hi @otykier,

What version of TE2 would I need to revert to, to get around this issue? Thanks.

@otykier - never mind, the previous version works fine. 👍

[christianwade]

This issue should be fixed in the version below. Note, this build is not digitally signed but you are free to use it.

https://github.com/microsoft/Analysis-Services/releases/tag/5.1.12-PreRelease

[pfab0]

Hi @christianwade, could you please share the ETA for the digitally signed 5.1.14 (or newer) release ?

[christianwade]

Hi @pfab0 , hopefully by the end of calendar year 2025. Digitial signing suddenly became harder ...

[christianwade]

Included in prod release, which is digitally signed:
https://github.com/microsoft/Analysis-Services/releases/tag/5.1.20