Can the Search API have different endpoints for each element (Subject, Action, Resource)?

[identitymonk]

While the example are not normative, the search endpoint definition differs per element:

• POST /access/v1/search/subject HTTP/1.1
• POST /access/v1/resource/search HTTP/1.1
• POST /access/v1/search/action HTTP/1.1

Note the different path approach for resource.

Question: is this explicit or a typo? should the search API accepts 3 different endpoints?

[identitymonk]

this will have an impact on the PDP Metadata document

[identitymonk]

somewhat duplicate of #277 still going deeper on the question

[ogazitt]

The specific issue #277 is due to a typo.

At the same time, your more general question is a good one. I believe that the current way you set up the metadata document is reasonable - meaning, there is a /access/v1/search base url, which supports one or more of { subject, resource, action }. But alternately we could also define a separate entry for each one of these.

On the whole, I slightly prefer to give each of the search APIs a separate entry, since it will be slightly easier for a caller to find out the URL of, say, the resource search API by looking that up directly, rather than having to also check a capability array and then tack on the URL component.

[identitymonk]

Will reflect the point in the PDP metadata proposal

[identitymonk]

Assuming the same will apply to Partial Evaluation endpoint @ogazitt

[ogazitt]

I think we can resolve/close this based on our discussion today.

[ogazitt]

Resolved by #290