Return code is: 403, ReasonPhrase: Forbidden

What This Error Means

The repository rejected the request (403). Your credentials may be valid, but you are not authorized for that repository/path or operation.

How to Fix It

1. Identify the operation that triggers 403 (download vs deploy) and the exact repository URL.
2. If this is a deploy error, confirm distributionManagement points to the correct repository (snapshots vs releases) and that your credentials have deploy permission.
3. If this is a download error, confirm your token/user has read access to the repository and that the path isn't restricted by policy.
4. If your repository manager enforces IP allowlists or SSO rules, ensure the build environment is allowed and uses the correct auth method.
5. Retry after permissions/policy are corrected.

Why It Happens

• Your account/token lacks permission for the repository (read vs deploy permissions).
• You are deploying to a repository that is read-only or blocked by policy.
• Snapshot vs release mismatch (for example, deploying a -SNAPSHOT to a releases-only repository).
• Security controls (IP allowlists, WAF rules) block the request even with valid credentials.

How to Verify

1. Re-run the original Maven command and confirm the repository no longer returns 403.
2. Confirm Maven can download (or deploy) the artifacts that previously failed.

Manual authorization checks

1. Confirm whether the 403 happens on download (dependency resolution) or on deploy (mvn deploy).
2. Confirm the repository URL is the correct Maven repository endpoint (not a web UI URL).
3. Check effective settings to confirm which server id Maven will use: mvn -q help:effective-settings.
4. Run with debug logs to capture the exact URL being requested: mvn -X -DskipTests package (or mvn -X deploy).

Common CLI Output

[ERROR] Failed to transfer file: https://repo.example.com/repository/maven-releases/... Return code is: 403, ReasonPhrase: Forbidden.

[ERROR] Failed to deploy artifacts: Could not transfer artifact com.example:app:jar:1.0.0 from/to internal (https://repo.example.com/maven): Return code is: 403, ReasonPhrase: Forbidden.

Why Maven gets 403 responses

1. A 403 response means the server understood the request but refused to fulfill it.
2. Common causes include insufficient permissions, blocked paths, repository policy mismatches (snapshots vs releases), or security controls like IP allowlists.

Prevention Tips

• Use separate credentials for read vs deploy and scope them to the minimum required permissions.
• Clearly separate snapshot and release repositories and enforce consistent versioning practices.
• Centralize access through a repository manager so authorization is consistent across environments.

Where This Can Be Triggered

String msg = "Could not resolve dependencies for project " + project.getId() + ": " + e.getMessage();
DependencyResolutionException dex = new DependencyResolutionException(msg, e);
dex.setResult(e.getResult());
throw dex;