libre.sh/keycloak-scim
2
0
Fork 0
Code Issues 14 Pull requests Releases Packages Activity Actions 6

requested updates

Browse source
This commit is contained in:
Matthew Helmke 2019-01-17 07:49:05 -06:00
parent 95bc91b80b
commit 50f5205e93
2 changed files with 10 additions and 10 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
upgrading/topics/rhsso/changes-72.adoc
View file

@ -48,11 +48,11 @@ described in <<_compatibility_with_older_adapters>>. There is the `Exclude Sessi
which can be turned on to prevent adding the `session_state` parameter to the Authentication Response. which can be turned on to prevent adding the `session_state` parameter to the Authentication Response.
=== Microsoft Identity Provider updated to use the Microsoft Graph API === Microsoft Identity Provider updated to use the Microsoft Graph API
The Microsoft Identity Provider implementation in {project_name} up to version 7.2.4 relies on the Live SDK The Microsoft Identity Provider implementation in {project_name} used to rely on the Live SDK
endpoints for authorization and obtaining the user profile. From November 2018 onwards, Microsoft is removing support 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 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 7.2.5 or later. to use the new endpoints so if this integration is in use make sure you upgrade to the latest {project_name} version.
Legacy client applications registered under "Live SDK applications" won't work with the Microsoft Graph endpoints 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 due to changes in the id format of the applications. If you run into an error saying that the application identifier
@ -61,10 +61,10 @@ https://account.live.com/developers/applications/create[Microsoft Application Re
=== Google Identity Provider updated to use Google Sign-in authentication system === Google Identity Provider updated to use Google Sign-in authentication system
The Google Identity Provider implementation in {project_name} up to version 7.2.5 relies on the Google+ API endpoints The Google Identity Provider implementation in {project_name} used to rely on the Google+ API endpoints
endpoints for authorization and obtaining the user profile. From March 2019 onwards, Google is removing support endpoints for authorization and obtaining the user profile. From March 2019 onwards, Google is removing support
for the Google+ API in favor of the new Google Sign-in authentication system. The {project_name} identity provider has been updated for the Google+ API in favor of the new Google Sign-in authentication system. 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 7.2.6 or later. to use the new endpoints so if this integration is in use make sure you upgrade to the latest {project_name} version.
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 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://console.developers.google.com/apis/credentials[Google API Console] portal to obtain a new application id and secret. https://console.developers.google.com/apis/credentials[Google API Console] portal to obtain a new application id and secret.

10
upgrading/topics/rhsso/changes-73.adoc
View file

@ -126,11 +126,11 @@ the native promise. This was causing issues as the error handler was not always
resulted in `Uncaught (in promise)` error. resulted in `Uncaught (in promise)` error.
=== Microsoft Identity Provider updated to use the Microsoft Graph API === Microsoft Identity Provider updated to use the Microsoft Graph API
The Microsoft Identity Provider implementation in {project_name} up to version 7.2 relies on the Live SDK The Microsoft Identity Provider implementation in {project_name} used to rely on the Live SDK
endpoints for authorization and obtaining the user profile. From November 2018 onwards, Microsoft is removing support 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 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 7.3 or later. to use the new endpoints so if this integration is in use make sure you upgrade to the latest {project_name} version.
Legacy client applications registered under "Live SDK applications" won't work with the Microsoft Graph endpoints 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 due to changes in the id format of the applications. If you run into an error saying that the application identifier
@ -139,10 +139,10 @@ https://account.live.com/developers/applications/create[Microsoft Application Re
=== Google Identity Provider updated to use Google Sign-in authentication system === Google Identity Provider updated to use Google Sign-in authentication system
The Google Identity Provider implementation in {project_name} up to version 7.2.5 relies on the Google+ API endpoints The Google Identity Provider implementation in {project_name} used to rely on the Google+ API endpoints
endpoints for authorization and obtaining the user profile. From March 2019 onwards, Google is removing support endpoints for authorization and obtaining the user profile. From March 2019 onwards, Google is removing support
for the Google+ API in favor of the new Google Sign-in authentication system. The {project_name} identity provider has been updated for the Google+ API in favor of the new Google Sign-in authentication system. 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 7.2.6 or later. to use the new endpoints so if this integration is in use make sure you upgrade to the latest {project_name} version.
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 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://console.developers.google.com/apis/credentials[Google API Console] portal to obtain a new application id and secret. https://console.developers.google.com/apis/credentials[Google API Console] portal to obtain a new application id and secret.