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

Credential production and monitoring for JWT access tokens #2424

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

benoitroland
Copy link

Development of a credential producer (in go-lang) and a credential monitor (in python) for the production, monitoring and refreshment of JWT access tokens. The Mytoken service is used for the renewal procedure. The setup has been tested for the Helmholtz AAI and Darwin AAI providers. Private rpms available for RHEL7 and RHEL8. Tested and deployed in production environment at KIT SCC. Development done at KIT SCC.

HTCondor Pull Request Checklist for internal reviewers

  • Verify that (GitHub thinks) the merge is clean. If it isn't, and you're confident you can resolve the conflicts, do so. Otherwise, send it back to the original developer.
  • Verify that the related Jira ticket exists and has a target version number and that it is correct.
  • Verify that the Jira ticket is in review status and is assigned to the reviewer.
  • Verify that the Jira ticket (HTCONDOR-xxx) is mentioned at the beginning of the title. Edit it, if not
  • Verify that the branch destination of the PR matches the target version of the ticket
  • Check for correctness of change
  • Check for regression test(s) of new features and bugfixes (if the feature doesn't require root)
  • Check for documentation, if needed (documentation build logs)
  • Check for version history, if needed
  • Check BaTLab dashboard for successful build (https://batlab.chtc.wisc.edu/results/workspace.php) and test for either the PR or a workspace build by the developer that has the Jira ticket as a comment.
  • Check that each commit message references the Jira ticket (HTCONDOR-xxx)

After the above

  • Hit the merge button if the pull request is approved and it is not a security patch (security changes require 2 additional reviews)
  • If the pull request is approved, take the ticket out of review state
  • Assign JIRA Ticket back to the developer

@benoitroland
Copy link
Author

Dear @bbockelm, @jasoncpatton, @GregThain, @giffels, this message to tell you that I have updated my pull request for the production and monitoring of JWT access tokens. The setup has been tested for the Helmholtz AAI and Darwin AAI providers. Private rpms available for RHEL7 and RHEL8 have been tested and deployed in production environment at KIT SCC. I am sorry for opening a new pull request. Renaming my branch has closed the previous one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant