| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
There was a problem hiding this comment.
works for me!
Sorry, something went wrong.
There was a problem hiding this comment.
Elegant
Sorry, something went wrong.
There was a problem hiding this comment.
None of the tests cover cases where either multiple modes or purposes are set, would it be worth adding one?
Sorry, something went wrong.
| * @return the resource, may be {@code null} | ||
| */ | ||
| public URI getResource() { | ||
| return resource; |
There was a problem hiding this comment.
Even if it may not be supported by all Access Management Applications, an Access Grant may cover multiple resources. Is it something that should be reflected in the querying capabilities? Or do we want to push this constraint down to the client libraries, in which case we should consider the same for the JC client.
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
This adds an AccessCredentialQuery class to make it easier to add permutations to the query interface. In particular, this makes it possible to add multiple access modes ("Read", "Write") and purpose identifiers to a query.
Otherwise, one needs to make multiple requests with the client and manage the set operations manually.
This builder looks like this: