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

[RHSSO-1225] - Informing deprecation of UMA 1.0

Browse source
This commit is contained in:
pedroigor 2018-01-30 17:25:41 -02:00
parent 563d219724
commit 006a58eb41
2 changed files with 25 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
authorization_services/topics/auth-services-overview.adoc
View file

@ -3,6 +3,7 @@
:tech_feature_name: Authorization Services :tech_feature_name: Authorization Services
include::templates/techpreview.adoc[] include::templates/techpreview.adoc[]
include::templates/authz-service-deprecated-features.adoc[]
{project_name} supports fine-grained authorization policies and is able to combine different access control {project_name} supports fine-grained authorization policies and is able to combine different access control
mechanisms such as: mechanisms such as:

24
topics/templates/authz-service-deprecated-features.adoc Normal file
View file

@ -0,0 +1,24 @@
ifeval::[{project_product}==true]
[WARNING]
====
In future releases we'll be updating User-Managed Access(UMA) implementation to conform
with the latest version of UMA specification, version 2.0.
Due to differences between versions 1.0 (currently supported) and 2.0 of UMA, we are deprecating specific functionalities
in order to keep compliance with the new version. Here is a list of deprecated features:
* *Entitlement API*
This REST API will be removed in future releases in favor of a more OAuth2 based way to obtain permissions from the server using a specific grant type. This grant type
is based on UMA 2.0 with extensions to make it work without permission tickets. Same behavior as Entitlement API.
* *Authorization API*
This REST API was removed by UMA working group in version 2.0. As a consequence, we'll be removing it too. It will
be replaced by a specific OAuth2 grant type as defined by UMA 2.0 specification.
Other changes are related with the Policy Enforcer, Authorization Client Java API and configuration. For these areas in particular changes are minimal, specially regarding policy enforcer configuration.
We'll be updating docs accordingly, specially on how to migrate to the new version.
====
endif::[]