You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Maven authentication information is stored in local settings.xml.
Considering the extractor uses virtual filesystem, we need to refactor MavenRegistryAPIClient to use the virtual filesystem to read the local settings.
settings.xml is read when we construct NewMavenRegistryAPIClient and the client is constructed when the extractor is constructed which is before Extract() is called.
The text was updated successfully, but these errors were encountered:
I discussed this with @michaelkedar earlier -- this is probably lower priority for now because auth only makes sense in the local developer use case where they have creds on their machine, and having a virtual filesystem isn't as necessary there.
cuixq
changed the title
Use virtual filesystem to read local Maven settings
Make sure Maven settings.xml are read correctly
Feb 10, 2025
What happens when we're scanning a remote container with SCALIBR? Would we expect the settings.xml be on the host that's running the scanner or on the container?
If it's on the remote container then this plugin wouldn't work for container scanning until we find a way to fix this
Maven authentication information is stored in local
settings.xml
.Considering the extractor uses virtual filesystem, we need to refactor
MavenRegistryAPIClient
to use the virtual filesystem to read the local settings.settings.xml
is read when we constructNewMavenRegistryAPIClient
and the client is constructed when the extractor is constructed which is beforeExtract()
is called.The text was updated successfully, but these errors were encountered: