John Erickson
John Erickson
Ideally, we'd have a consistent way to connect the `ExternalDocumentRef` and the `File`. Maybe `DESCRIBES`? https://spdx.github.io/spdx-spec/7-relationships-between-SPDX-elements/
Might not need this if we do https://github.com/AzureAD/microsoft-authentication-library-for-dotnet/pull/3593
Thanks so much!
I think this is the missing piece of the puzzle. I will privately build and test with https://github.com/Microsoft/artifacts-credprovider/tree/broker
I am hitting this in Ubuntu 20, but not on 22. I think it may have been addressed as part of https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929656
Yes, I was thinking more about the code side of things. I think MSYS/MinGW will be the easiest as it already supports a lot (e.g. pthreads). I've made some progress...
And MSYS/MinGW uses ./configure && make directly.
Similarly, if I am logged in as `[email protected]` and I say, `app.AcquireTokenSilent(scopes, loginHint: "[email protected]")` it should just work. Right now, I have to explicitly compare the loginHint to the current...
I see three different ways to login as the current user: 1. `AcquireTokenByIntegratedWindowsAuthentication` 2. `AcquireTokenSilent(PublicClientApplication.OperatingSystemAccount)` 3. `AcquireTokenSilent( loginHint: currentUser.ToString())` Ideally there would be 1 API that MSAL consumers would call...
Increasing the sample size to 2 😁 I've confirmed on my Windows laptop as well: 