Simplify Sonatype Maven repository authentication#9
Merged
Conversation
The Central Portal snapshot repository (maven-snapshots) uses standard basic authentication (username/password), not Bearer token auth. Bearer is for the Portal API and OSSRH Staging API, but the snapshot repo is a standard Maven repository. https://claude.ai/code/session_0185eQCsjR2uRsGWn2JpU9Xr
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Simplified the authentication mechanism for the Sonatype Maven Central Portal snapshots repository by switching from custom HTTP header-based authentication to standard Maven credentials.
Key Changes
Base64import that was only used for manual token encodingHttpHeaderCredentialswith standard MavencredentialsblockHttpHeaderAuthenticationconfigurationsonatypeUsernameandsonatypePasswordproperties directlyImplementation Details
The authentication now leverages Maven's built-in credential handling instead of manually constructing Base64-encoded Bearer tokens. This approach is simpler, more maintainable, and aligns with standard Maven repository authentication practices. The credentials are still sourced from the same
sonatypeUsernameandsonatypePasswordproperties.https://claude.ai/code/session_0185eQCsjR2uRsGWn2JpU9Xr