Description of problem: You cannot use the Workbench's Maven Repository from external clients. Version-Release number of selected component (if applicable): 6.0.x Steps to Reproduce: 1. Launch the workbench and build "mortgages" example 2. Delete mortgages/mortgages/0.0.1 from your local .m2 (this ensures it only resides in the Workbench's Maven Repository) 3. Create a new dummy maven project 4. Add a <repository> entry to the pom for the Workbench Maven Repository 5. Add a dependency for mortgages:mortgages:0.0.1 6. Build dummy project from CLI 7. You'll get an authorization exception 8. Try adding credentials to Maven's setting.xml 9. Repeat step 6.. you still get the exception Actual results: See step 7 above. Expected results: The Workbench's Maven Repository should be accessible; either publicly - without need for authentication - or with authentication specified in setting.xml Additional info: If you add an exclusion to url_filter.yaml for /maven2/** authentication for the Workbench's Maven Repository is removed and artifacts deployed to it become accessible.
Michael, we need to secure the repo as per ticket 996393.
(In reply to Edson Tirelli from comment #4) > Michael, we need to secure the repo as per ticket 996393. +1, we should apply authentication to the repo with no default credentials.
All you need is configure your settings.xml with http preemptive set to true. Here an example for users of maven 3.1.1 <server> <id>my-kie-wb-server</id> <username>user</username> <password>password</password> <configuration> <wagonProvider>httpclient</wagonProvider> <httpConfiguration> <all> <usePreemptive>true</usePreemptive> </all> </httpConfiguration> </configuration> </server>
Verified on BRMS 6.0.0 ER7. The Workbench repository is accessible to maven, KIE-CI is unable to access it, but it seems to be a problem on KIE-CI side.
the 6.0.1.Final version of kie-ci doesn't have the auth function implemented. From the version 6.1.beta3 onwards it works just fine.