Confusing UMA permission management endpoint #13798

pckhoi · 2022-08-16T01:30:09Z

pckhoi
Aug 16, 2022

According to documentation, the path /authz/protection/uma-policy/ sometimes ends with resource_id:

curl -X POST \
  http://localhost:8180/realms/photoz/authz/protection/uma-policy/{resource_id} \
  -H 'Authorization: Bearer '$access_token \
  -H 'Cache-Control: no-cache' \
  -H 'Content-Type: application/json' \
  -d '{
        "name": "Any people manager",
        "description": "Allow access to any people manager",
        "scopes": ["read"],
        "condition": "my-deployed-script.js"
}'

And sometimes ends with permission_id:

curl -X PUT \
  http://localhost:8180/realms/photoz/authz/protection/uma-policy/{permission_id} \
  -H 'Authorization: Bearer '$access_token \
  -H 'Content-Type: application/json' \
  -d '{
    "id": "21eb3fed-02d7-4b5a-9102-29f3f09b6de2",
    "name": "Any people manager",
    "description": "Allow access to any people manager",
    "type": "uma",
    "scopes": [
        "album:view"
    ],
    "logic": "POSITIVE",
    "decisionStrategy": "UNANIMOUS",
    "owner": "7e22131a-aa57-4f5f-b1db-6e82babcd322",
    "roles": [
        "user"
    ]
}'

I wonder what the rationale behind this pathing scheme is. I know that this API isn't trying to be restful but it makes me question whether I'm seeing typos for quite a while.

Zikoel · 2022-09-21T10:56:12Z

Zikoel
Sep 21, 2022

I'm on this right now! I try with an hipotesys: The first is for manage resource-based permission, the second instedad for scope-based permission. My two cents.

0 replies

Navigation Menu

Repository navigation

Confusing UMA permission management endpoint #13798

Uh oh!

{{title}}

Uh oh!

Replies: 1 comment

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

Confusing UMA permission management endpoint #13798

Uh oh!

pckhoi Aug 16, 2022

Replies: 1 comment

Uh oh!

Zikoel Sep 21, 2022

pckhoi
Aug 16, 2022

Zikoel
Sep 21, 2022