ADAL to MSAL migration - ID Token missing #1694
-
Hi Team, I am trying to migrate from ADAL to MSAL. In MSAL Thanks in advance. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
While constructing PublicClientApplication, when you use MSAL, you instantiate a PublicClientApplication. This object models your app identity and is used to make requests to one or more authorities. With this object you will configure your client identity, redirect URI, default authority, whether to use the device browser vs. embedded web view, the log level, and more. You can declaratively configure this object with JSON, which you either provide as a file or store as a resource within your APK. Although this object is not a singleton, internally it uses shared Executors for both interactive and silent requests. In ADAL, every organization that you request access tokens from requires a separate instance of the AuthenticationContext. In MSAL, this is no longer a requirement. You can specify the authority from which you want to request a token as part of your silent or interactive request. For more information you can follow these links: |
Beta Was this translation helpful? Give feedback.
-
@rkrsgithub In MSAL, you can get ID Token as follows:
|
Beta Was this translation helpful? Give feedback.
While constructing PublicClientApplication, when you use MSAL, you instantiate a PublicClientApplication. This object models your app identity and is used to make requests to one or more authorities. With this object you will configure your client identity, redirect URI, default authority, whether to use the device browser vs. embedded web view, the log level, and more.
You can declaratively configure this object with JSON, which you either provide as a file or store as a resource within your APK.
Although this object is not a singleton, internally it uses shared Executors for both interactive and silent requests.
In ADAL, every organization that you request access tokens from requires a …