feat(prism-agent): add JWT auth support for agent-admin role
prism-agentbuild
# Overview ATL-6074. This PR adds a concept of `EntityRole` to `Entity` and `KeycloakEntity` to implement the admin role authentication of both JWT and admin-api-key following this [ADR](https://github.com/hyperledger-labs/open-enterprise-agent/blob/main/docs/decisions/20240103-use-jwt-claims-for-agent-admin-auth.md). ## Checklist ### My PR contains... * [ ] No code changes (changes to documentation, CI, metadata, etc.) * [ ] Bug fixes (non-breaking change which fixes an issue) * [ ] Improvements (misc. changes to existing features) * [x] Features (non-breaking change which adds functionality) ### My changes... * [ ] are breaking changes * [x] are not breaking changes * [ ] If yes to above: I have updated the documentation accordingly ### Documentation * [ ] My changes do not require a change to the project documentation * [x] My changes require a change to the project documentation * [ ] If yes to above: I have updated the documentation accordingly ### Tests * [ ] My changes can not or do not need to be tested * [x] My changes can and should be tested by unit and/or integration tests * [x] If yes to above: I have added tests to cover my changes * [ ] If yes to above: I have taken care to cover edge cases in my tests
[![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=follow-redirects&package-manager=npm_and_yarn&previous-version=1.15.2&new-version=1.15.4)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/hyperledger-labs/open-enterprise-agent/network/alerts). </details> </td> </tr> </table>
# Overview Fixes ATL-6268 - improve OpenAPI specification for Verification Policies API ## Checklist ### My PR contains... * [x] No code changes (changes to documentation, CI, metadata, etc.) * [ ] Bug fixes (non-breaking change which fixes an issue) * [x] Improvements (misc. changes to existing features) * [ ] Features (non-breaking change which adds functionality) ### My changes... * [ ] are breaking changes * [x] are not breaking changes * [ ] If yes to above: I have updated the documentation accordingly ### Documentation * [x] My changes do not require a change to the project documentation * [ ] My changes require a change to the project documentation * [ ] If yes to above: I have updated the documentation accordingly ### Tests * [x] My changes can not or do not need to be tested * [ ] My changes can and should be tested by unit and/or integration tests * [ ] If yes to above: I have added tests to cover my changes * [ ] If yes to above: I have taken care to cover edge cases in my tests
# Overview https://input-output.atlassian.net/browse/ATL-6320 ## Checklist ### My PR contains... * [ ] No code changes (changes to documentation, CI, metadata, etc.) * [ ] Bug fixes (non-breaking change which fixes an issue) * [ ] Improvements (misc. changes to existing features) * [x] Features (non-breaking change which adds functionality) ### My changes... * [ ] are breaking changes * [x] are not breaking changes * [ ] If yes to above: I have updated the documentation accordingly ### Documentation * [ ] My changes do not require a change to the project documentation * [x] My changes require a change to the project documentation * [ ] If yes to above: I have updated the documentation accordingly ### Tests * [ ] My changes can not or do not need to be tested * [x] My changes can and should be tested by unit and/or integration tests * [x] If yes to above: I have added tests to cover my changes * [x] If yes to above: I have taken care to cover edge cases in my tests
# Overview Fixes ATL-6269 ## Checklist ### My PR contains... * [ ] No code changes (changes to documentation, CI, metadata, etc.) * [ ] Bug fixes (non-breaking change which fixes an issue) * [ ] Improvements (misc. changes to existing features) * [ ] Features (non-breaking change which adds functionality) ### My changes... * [ ] are breaking changes * [ ] are not breaking changes * [ ] If yes to above: I have updated the documentation accordingly ### Documentation * [ ] My changes do not require a change to the project documentation * [ ] My changes require a change to the project documentation * [ ] If yes to above: I have updated the documentation accordingly ### Tests * [ ] My changes can not or do not need to be tested * [ ] My changes can and should be tested by unit and/or integration tests * [ ] If yes to above: I have added tests to cover my changes * [ ] If yes to above: I have taken care to cover edge cases in my tests