Skip to content

Commit c264f2f

Browse files
committed
Merge branch 'dev' of git@github.com:unity-idm/unity.git into dev
2 parents 110dd3b + 689a0a1 commit c264f2f

File tree

1 file changed

+16
-5
lines changed

1 file changed

+16
-5
lines changed

documentation/src/main/doc/endpoint-oauth.txt

Lines changed: 16 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,7 @@ client:
5757
- must possess the +sys:oauth:allowedReturnURI+ attribute (in OAuth clients group) with allowed return URI(s),
5858
- can have logo and/or displayed name OAuth attributes assigned to improve client's presentation during user's consent.
5959
- should have an attribute +sys:oauth:clientType+ specifying whether the client is confidential or public. By
60-
default client is assumed to be confidential, if the attribute is unset.
60+
default, client is assumed to be confidential, if the attribute is unset.
6161

6262
OAuth users must belong to a group specified in the configuration file. If no restrictions are required the '/' group
6363
can be used. In case that there are different groups of users for different OAuth clients, those groups can be
@@ -66,7 +66,7 @@ configured with client's attribute +sys:oauth:groupForClient+.
6666
OAuth scopes should be defined next. Each scope includes a list of Unity attributes (use the Unity name) that should be
6767
exposed when the client asks for the scope and the user gives her consent.
6868

69-
Finally an output translation profile can be configured. It is highly useful to map Unity's internal attribute names
69+
Finally, an output translation profile can be configured. It is highly useful to map Unity's internal attribute names
7070
to names used by OAauth consumers. Standard OAuth/OIDC attribute names can be found in the OIDC specification:
7171
http://openid.net/specs/openid-connect-core-1_0.html#StandardClaims
7272

@@ -236,10 +236,9 @@ authorized with the token in question. This feature is very useful in case of st
236236
is reduced to access token verification.
237237

238238
To enable this feature set accessToken validity to a proper short time (e.g. 30 minutes) - equal to the intended inactive login session
239-
time. Additionally set +extendAccessTokenValidityUpTo+ to the intended longest session time (e.g. 12 hours). Then the actively used
239+
time. Additionally, set +extendAccessTokenValidityUpTo+ to the intended longest session time (e.g. 12 hours). Then the actively used
240240
access token can be valid for up to 12 hours, but will automatically expire after 30 minutes without use.
241241

242-
243242
==== Public and native clients, PKCE
244243

245244
Unity supports _Proof Key for Code Exchange by OAuth Public Clients OAuth 2.0 for Native Apps_
@@ -253,8 +252,20 @@ Note that the path must still match exactly.
253252
* The +http+ scheme can be used in case of IP based loopback redirect, even if +https+ is configured in authorized return URI.
254253
* Consent screen acceptance can not be saved - it is always presented.
255254

256-
See the aformentioned RFCs for details on how to use PKCE,
255+
See the aforementioned RFCs for details on how to use PKCE,
257256
and what forms of return redirections are available for native clients.
258257

259258

259+
==== Client-Requested Claim Value Filtering
260+
261+
Unity supports a proprietary feature that allows OAuth clients to request filtering of claim values. This feature is activated when the client uses a special scope prefixed with +claim_filter:+, as follows:
262+
263+
----
264+
scope=profile%20claim_filter:entitlements:abc
265+
----
266+
267+
In this example, one regular scope +profile+ is requested, as well as one claim value filter. If the +entitlements+ claim is returned as part of the +profile+ scope, only its +abc+ value is included. If the +entitlements+ claim has no +abc+ value, it is not returned.
268+
269+
Multiple claim value filters can be used together, even for the same claim. These filters function as a whitelist: every value matching a filter is returned.
260270

271+
Note that when requesting a refresh token, a client may change (or completely omit) claim filters.

0 commit comments

Comments
 (0)