microsoft-authentication-library-for-go
microsoft-authentication-library-for-go copied to clipboard
AzureAD
The MSAL library for Go is part of the Microsoft identity platform for developers (formerly named Azure AD) v2.0. It enables you to acquire security tokens to call protected APIs. It uses industry sta...
Add tests to parse a sample mex doc to verify mex parsing is working as expected.
For auth code/interactive auth with PKCE, the `code_challenge` query param is sent however its value can change depending on the "leg" of the flow. For the first leg (e.g. interactive...
This has become a bit of a grab-bag of data used for a few different flows. It works, but it's not clear where/when each part is used which could lead...
Recent change to support custom HTTP clients means that the authority endpoints will be cached per confidential client. Investigate if the endpoint caching should be consolidated.
Refer : https://github.com/AzureAD/microsoft-authentication-library-for-go/pull/117/files/7eb5b4519a229198822a8c808f9d0d2fe9ce85ac#r553583397 These parameters are commented at this moment but can be added back when implementing interactive auth flow with PKCE
The library has support for pem encoded PKCS8 private key. Investigate and add support for other types. I tried using a PEM encoded RSA Private key in PKCS1 and it...
These are some of the pages that should be updated (there are more) https://docs.microsoft.com/en-us/azure/active-directory/develop/scenario-web-app-sign-user-app-configuration? https://docs.microsoft.com/en-us/azure/active-directory/develop/scenario-web-app-call-api-app-configuration? https://docs.microsoft.com/en-us/azure/active-directory/develop/scenario-desktop-app-configuration?https://docs.microsoft.com/en-us/azure/active-directory/develop/scenario-daemon-app-configuration?
Create a quick start, concept to be found here: Javascript quickstart, notice how we are using tags for what goes to the portal and docs. https://docs.microsoft.com/en-us/azure/active-directory/develop/quickstart-v2-javascript The md file from...
Per [rfc8628](https://tools.ietf.org/html/rfc8628#section-3.5), client polling access token might get a `expired_token` response: > The "device_code" has expired, and the device authorization session has concluded. The client MAY commence a new device...
config.json doesn't need client secret & confidential.json doesn't need username/password for example.
