KEYCLOAK-6757 Update MicrosoftIdentityProvider to use the Microsoft Graph API
This commit is contained in:
parent
10b2f2ef9a
commit
15b2ea8860
3 changed files with 29 additions and 1 deletions
|
@ -32,3 +32,19 @@ You'll have to copy the `Redirect URI` from the {project_name} `Add Identity Pro
|
|||
Finally, you will need to obtain the Application ID and secret from this page so you can enter them back on the {project_name} `Add identity provider` page.
|
||||
Go back to {project_name} and specify those items.
|
||||
|
||||
ifeval::[{project_community}==true]
|
||||
WARNING: From November 2018 onwards, Microsoft is removing support for the Live SDK API in favor of the new Microsoft Graph API.
|
||||
The {project_name} Microsoft identity provider has been updated to use the new endpoints so make sure to upgrade to
|
||||
{project_name} version 4.6.0 or later in order to use this provider.
|
||||
Furthermore, client applications registered with Microsoft under "Live SDK applications" will need to be re-registered
|
||||
in the https://apps.dev.microsoft.com/[Microsoft Application Registration] portal to obtain an application id that
|
||||
is compatible with the Microsoft Graph API.
|
||||
endif::[]
|
||||
ifeval::[{project_product}==true]
|
||||
WARNING: From November 2018 onwards, Microsoft is removing support for the Live SDK API in favor of the new Microsoft Graph API.
|
||||
The {project_name} Microsoft identity provider has been updated to use the new endpoints so make sure to upgrade to
|
||||
{project_name} version 7.2.5 or later in order to use this provider.
|
||||
Furthermore, client applications registered with Microsoft under "Live SDK applications" will need to be re-registered
|
||||
in the https://apps.dev.microsoft.com/[Microsoft Application Registration] portal to obtain an application id that
|
||||
is compatible with the Microsoft Graph API.
|
||||
endif::[]
|
||||
|
|
|
@ -29,6 +29,18 @@ In the past if native promise was available a wrapper was returned that provided
|
|||
the native promise. This was causing issues as the error handler was not always set prior to the native error event, which
|
||||
resulted in `Uncaught (in promise)` error.
|
||||
|
||||
==== Microsoft Identity Provider updated to use the Microsoft Graph API
|
||||
|
||||
The Microsoft Identity Provider implementation in {project_name} up to version 4.5.0 relies on the Live SDK
|
||||
endpoints for authorization and obtaining the user profile. From November 2018 onwards, Microsoft is removing support
|
||||
for the Live SDK API in favor of the new Microsoft Graph API. The {project_name} identity provider has been updated
|
||||
to use the new endpoints so if this integration is in use make sure you upgrade to {project_name} version 4.6.0 or later.
|
||||
|
||||
Legacy client applications registered under "Live SDK applications" won't work with the Microsoft Graph endpoints
|
||||
due to changes in the id format of the applications. If you run into an error saying that the application identifier
|
||||
was not found in the directory, you will have to register the client application again in the
|
||||
https://apps.dev.microsoft.com/[Microsoft Application Registration] portal to obtain a new application id.
|
||||
|
||||
=== Migrating to 4.4.0
|
||||
|
||||
==== Upgrade to Wildfly 13
|
||||
|
|
|
@ -6,4 +6,4 @@ This guide describes how to upgrade {project_name}. It is recommended that you s
|
|||
server first and {project_name} adapters second.
|
||||
|
||||
Before upgrading make sure to read the instructions carefully and carefully review the changes listed in
|
||||
<<migration-changes,Migration Chanages>>.
|
||||
<<migration-changes,Migration Changes>>.
|
Loading…
Reference in a new issue