OAuth 2.0-based authentication of users and devices, user profile management, Single Sign-On (SSO) and Identity Federation across multiple administration domains.
When using the internal Keyrock authorization registry, it is possible to request whether a subject has the access rights to execute a specific action on a specific resource. Service providers which are allowed to provide services to the subject can also be configured, but querying on this attribute throws an error and returns status code 500 to the user of the api. This PR changes a non-existent method (has) to its implemented equivalent (includes), such that the code doesn't crash anymore.
Types of changes
[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality
to not work as expected)
Proposed changes
When using the internal Keyrock authorization registry, it is possible to request whether a subject has the access rights to execute a specific action on a specific resource. Service providers which are allowed to provide services to the subject can also be configured, but querying on this attribute throws an error and returns status code 500 to the user of the api. This PR changes a non-existent method (
has
) to its implemented equivalent (includes
), such that the code doesn't crash anymore.Types of changes
Checklist
Further comments
Problem can also be seen in this forum post: https://spaces.fundingbox.com/spaces/i4trust-i4trust-helpdesk/648daadfb958a4312734000c