This is in relation to https://www.keycloak.org/docs/latest/authorization_services/index.html#_service_obtaining_permissions.
I think this might be a bug, but I'm not sure.

I have defined two "Resources", one called "Namespaces" and one called "Pipelines". The URI patterns are /Namespaces/* and /Pipelines/* respectively. There is a scope called Read, and it is associated with both resources.

I have written policies and permissions such that a client has permissions on "Namespaces" but not on "Pipelines".

I am using gocloak to explore evaluation of these, using "uri" format for the requests, with pattern matching.

First, for the "Namespaces" resource on its own. Evaluating with response-type=decision I get:

Request:
map[audience:[authorization-client] grant_type:[urn:ietf:params:oauth:grant-type:uma-ticket] permission:[/Namespaces/Namespace1#Read] permission_resource_format:[uri] permission_resource_matching_uri:[true] response_include_resource_name:[true] response_mode:[decision]]
Response:
{"result":true}

Then, response-type=permissions:

Request:
map[audience:[authorization-client] grant_type:[urn:ietf:params:oauth:grant-type:uma-ticket] permission:[/Namespaces/Namespace1#Read] permission_resource_format:[uri] permission_resource_matching_uri:[true] response_include_resource_name:[true] response_mode:[permissions]]
Response:
[{"rsid":"0c07df2d-4c10-4726-b38f-92f7355956e2","rsname":"Namespaces","scopes":["Read"]}]

So this is working as expected.

The for the "Pipelines" resource:

Request:
map[audience:[authorization-client] grant_type:[urn:ietf:params:oauth:grant-type:uma-ticket] permission:[/Pipelines/Pipeline1#Read] permission_resource_format:[uri] permission_resource_matching_uri:[true] response_include_resource_name:[true] response_mode:[permissions]]
403 Forbidden: access_denied: not_authorized

Request:
map[audience:[authorization-client] grant_type:[urn:ietf:params:oauth:grant-type:uma-ticket] permission:[/Pipelines/Pipeline1#Read] permission_resource_format:[uri] permission_resource_matching_uri:[true] response_include_resource_name:[true] response_mode:[decision]]
403 Forbidden: access_denied: not_authorized

Again, this is working as expected. I've not set up any permissions granting access to the "Pipelines" resource.

Now, try both together. First requesting "permissions:

Request:
map[audience:[authorization-client] grant_type:[urn:ietf:params:oauth:grant-type:uma-ticket] permission:[/Namespaces/Namespace1#Read /Pipelines/Pipeline1#Read] permission_resource_format:[uri] permission_resource_matching_uri:[true] response_include_resource_name:[true] response_mode:[permissions]]
Response:
[{"rsid":"0c07df2d-4c10-4726-b38f-92f7355956e2","rsname":"Namespaces","scopes":["Read"]}]

(The output here is slightly ambiguous. The field "permission" has a value that is an array of two values. When encoded for the body of the request it is permission=%2FNamespaces%2FNamespace1%23Read&permission=%2FPipelines%2FPipeline1%23Read, so I'm fairly sure that the actual body of the request has the correct content).

So this is my first confusion. I can understand the output here in a way. It's returning me all of the resources I have permissions to, and what permissions I have. However, I have no way of relating that back to the original request, since the request was made in URI format. There's no way I can tell that /Namespaces/Namespace1#Read was granted and that /Pipelines/Pipeline1#Read was not. As a human you can tell, but only because you know what resources have been set up. But the code doesn't have that knowledge, since it's matching via URIs.
I suspect that what the intention here is that I'm asking whether I have permission for both uris, and it is supposed to return me an OK response only if permission to both is granted. If that's the case, then this appears to be returning the wrong answer.

I wondered whether there was some issue with the way that the request was being constructed or parsed, such that the keycloak code only saw one of those permissions. However, it doesn't appear to make a difference which way round the permissions are requested.

Then requesting just the decision:

Request:
map[audience:[authorization-client] grant_type:[urn:ietf:params:oauth:grant-type:uma-ticket] permission:[/Namespaces/Namespace1#Read /Pipelines/Pipeline1#Read] permission_resource_format:[uri] permission_resource_matching_uri:[true] response_include_resource_name:[true] response_mode:[decision]]
Response:
{"result":true}

Surely this output is just plain wrong? I've asked for permission to access to two things, one of which I have access to and one of which I don't and the response is "Yes, sure, go ahead!".

Now maybe I'm not understanding the purpose of the API. My assumption is that the semantics of passing multiple permissions is supposed to be "AND", rather than perhaps treating them as independent for example. However, if this is the case, this appears not to work, or the request is supposed to be presented in a different form than &permission=permission&permission=permission2