-
Notifications
You must be signed in to change notification settings - Fork 191
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
Authentication fails when trying to resolve a target platform over an authenticated mirror that is a composite repository #3501
Comments
@kevloral yes composited that points to childs below the base dir are a bit tricky.
Thanks, I plan to make a new bugfix release soon, do you have an estimate so we can probably wait for your fix to be included? |
As thsi bugfix release is aimed for 4.31 Platform build to not use snapshot Tycho 4.x release would have to be out next Monday (Feb 19th) at the very latest in order to have couple of days to propagate things to the RC1 build. |
- testTargetDefinitionAuthMirror: tries to resolve a target definition from a composite p2 repository accessed over an authenticated composite mirror. - testTargetDefinitionEncrypted: tries to resolve a target definition from an authenticated composite p2 repository whose password is encrypted. Several others have been created for completion,
I have updated the title given that the problem occurs when trying to resolve a target platform using a p2 composite repository that requires authentication, no matter whether it is acting as a mirror (testTargetDefinitionAuthMirror) or not (testTargetDefinitionEncrypted). |
- testTargetDefinitionAuthMirror: tries to resolve a target definition from a composite p2 repository accessed over an authenticated composite mirror. - testTargetDefinitionEncrypted: tries to resolve a target definition from an authenticated composite p2 repository whose password is encrypted. Several others have been created just for completion: - testAuthMirror: tries to access a composite p2 repository over an authenticated composite mirror. - testMirror: tries to access a composite p2 repository over a composite mirror with no authentication. - testRepositoryEncrypted: tries to access an authenticated composite p2 repository whose password is encrypted. - testTargetDefinition: tries to resolve a target platform from a composite p2 repository. - testTargetDefinitionMirror: tries to resolve a target definition from a composite p2 repository accessed over a composite mirror with no authentication.
I have restored the previous title, given that test testTargetDefinitionEncrypted was failing for a completely different reason (that has already been fixed). |
- testTargetDefinitionAuthMirror: tries to resolve a target definition from a composite p2 repository accessed over an authenticated composite mirror. Several others have been created just for completion: - testAuthMirror: tries to access a composite p2 repository over an authenticated composite mirror. - testMirror: tries to access a composite p2 repository over a composite mirror with no authentication. - testRepositoryEncrypted: tries to access an authenticated composite p2 repository whose password is encrypted. - testTargetDefinition: tries to resolve a target platform from a composite p2 repository. - testTargetDefinitionEncrypted: tries to resolve a target definition from an authenticated composite p2 repository whose password is encrypted. - testTargetDefinitionMirror: tries to resolve a target definition from a composite p2 repository accessed over a composite mirror with no authentication.
RemoteMetadataRepositoryManager now passes the effective URI to the MavenAuthenticator instead of the original one. This fixes eclipse-tycho#3501. This commit also includes the test that was used to reproduce the bug: - testTargetDefinitionAuthMirror: tries to resolve a target definition from a composite p2 repository accessed over an authenticated composite mirror. Also, several other tests have been created just for completion: - testAuthMirror: tries to access a composite p2 repository over an authenticated composite mirror. - testMirror: tries to access a composite p2 repository over a composite mirror with no authentication. - testRepositoryEncrypted: tries to access an authenticated composite p2 repository whose password is encrypted. - testTargetDefinition: tries to resolve a target platform from a composite p2 repository. - testTargetDefinitionEncrypted: tries to resolve a target definition from an authenticated composite p2 repository whose password is encrypted. - testTargetDefinitionMirror: tries to resolve a target definition from a composite p2 repository accessed over a composite mirror with no authentication.
The PR that contains the fix for this issue is now ready to be reviewed: #3521 |
RemoteMetadataRepositoryManager now passes the effective URI to the MavenAuthenticator instead of the original one. This fixes eclipse-tycho#3501. This commit also includes the test that was used to reproduce the bug: - testTargetDefinitionAuthMirror: tries to resolve a target definition from a composite p2 repository accessed over an authenticated composite mirror. Also, several other tests have been created just for completion: - testAuthMirror: tries to access a composite p2 repository over an authenticated composite mirror. - testMirror: tries to access a composite p2 repository over a composite mirror with no authentication. - testRepositoryEncrypted: tries to access an authenticated composite p2 repository whose password is encrypted. - testTargetDefinition: tries to resolve a target platform from a composite p2 repository. - testTargetDefinitionEncrypted: tries to resolve a target definition from an authenticated composite p2 repository whose password is encrypted. - testTargetDefinitionMirror: tries to resolve a target definition from a composite p2 repository accessed over a composite mirror with no authentication.
Related to #2930, authentication still fails when the mirror that requires authentication is a composite repository . As a reminder, the mirror is declared like this in my Maven settings.xml file:
And its credentials are declared like this :
After the fixes we implemented in #2930, authentication works for the mirror itself, but still fails for the child locations it declares:
I will implement a test that reproduces the bug and propose a fix for it in a PR.
The text was updated successfully, but these errors were encountered: