Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

APPPOCTOOL-28 Use folio-auth-openid library for JWT validation #137

Merged
merged 2 commits into from
Sep 17, 2024

Conversation

pfilippov-epam
Copy link
Contributor

@pfilippov-epam pfilippov-epam commented Sep 16, 2024

Purpose

Injects and uses a common library for an authentication process.

Approach

  • Use folio-auth-openid as a dependency for JWT verification
  • Adjust unit and integration tests

TODOS and Open Questions

  • Check logging

Learning

Pre-Merge Checklist:

Before merging this PR, please go through the following list and take appropriate actions.

  • Does this PR meet or exceed the expected quality standards?
    • Code coverage on new code is 80% or greater
    • Duplications on new code is 3% or less
    • There are no major code smells or security issues
  • Does this introduce breaking changes?
    • Were any API paths or methods changed, added, or removed?
    • Were there any schema changes?
    • Did any of the interface versions change?
    • Were permissions changed, added, or removed?
    • Are there new interface dependencies?
    • There are no breaking changes in this PR.

If there are breaking changes, please STOP and consider the following:

  • What other modules will these changes impact?
  • Do Rally stories exist to update the impacted modules?
    • If not, please create them
    • Do they contain the appropriate level of detail? Which endpoints/schemas changed, etc.
    • Do they have all the appropriate links to blocked/related issues?
  • Are the Rally stories under active development?
    • If not, contact the project's PO and make sure they're aware of the urgency.
  • Do PRs exist for these changes?
    • If so, have they been approved?

Ideally, all the PRs involved in breaking changes would be merged on the same day to avoid breaking the folio-testing
environment. Communication is paramount if that is to be achieved, especially as the number of inter-module and
inter-team dependencies increase.

While it's helpful for reviewers to help identify potential problems, ensuring that it's safe to merge is ultimately the
responsibility of the PR assignee.

@pfilippov-epam pfilippov-epam requested a review from a team as a code owner September 16, 2024 09:46
Copy link

@pfilippov-epam pfilippov-epam merged commit e4a29b3 into master Sep 17, 2024
4 checks passed
@pfilippov-epam pfilippov-epam deleted the APPPOCTOOL-28 branch September 17, 2024 12:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants