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

Explicitly switch to Sonatype token authentication #23

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

rtyley
Copy link
Member

@rtyley rtyley commented Jan 16, 2024

As of January 2024, Sonatype is actively discouraging the legacy username & password method of authentication, recommending token authentication instead.

In this new scheme, the token is still split into a username/password format, and both are randomised strings, making the username portion a meaningful secret (ie one that can be revoked) and so worthy of being treated as a secret. Consequently, in this change username is now a GitHub workflow 'secret' parameter, rather than a simple input.

rtyley added a commit to rtyley/sample-project-using-gha-scala-library-release-workflow that referenced this pull request Jan 16, 2024
@rtyley rtyley force-pushed the use-sonatype-token-rather-than-username-password-auth branch 5 times, most recently from 69174f1 to 8bd424a Compare January 18, 2024 12:31
rtyley added a commit to guardian/etag-caching that referenced this pull request Jan 18, 2024
@rtyley rtyley force-pushed the use-sonatype-token-rather-than-username-password-auth branch 2 times, most recently from 4959e28 to a9d0967 Compare January 20, 2024 08:36
As of January 2024, Sonatype is actively discouraging the legacy
username & password method of authentication, recommending token
authentication instead:

* https://central.sonatype.org/news/20240109_issues_sonatype_org_deprecation/#support-requests
* https://central.sonatype.org/publish/generate-token/

In this new scheme, the token is still split into a username/password
format, and both are randomised strings, making the username portion
a meaningful secret (ie one that can be revoked) and so worthy of being
treated as a secret. Consequently, in this change username is now a
GitHub workflow 'secret' parameter, rather than a simple input.
@rtyley rtyley force-pushed the use-sonatype-token-rather-than-username-password-auth branch from a9d0967 to 8663357 Compare January 23, 2024 16:09
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.

None yet

1 participant