]
Mario Fusco resolved DROOLS-1366.
---------------------------------
Resolution: Rejected
The KieScanner doesn't know (and doesn't have a chance to know) how you created
the Resource passed to the KieContainer. You need to put those authorization credentials
in a maven settings.xml file and let the KieScanner use them by passing to it the name of
the file (if it is not the standard one in your user folder) as explained here
Cannot access remote KIE maven repo - Unauthorized access 401
-------------------------------------------------------------
Key: DROOLS-1366
URL:
https://issues.jboss.org/browse/DROOLS-1366
Project: Drools
Issue Type: Bug
Components: kie server
Reporter: Sambhaji Biradar
Assignee: Mario Fusco
Using the latest 6.5 version, we are getting unauthorized access error. From the other
posts I see that this issue was resolved in earlier versions but wondering if this issue
was introduced again in 6.5. I tried this solution with no success -
https://issues.jboss.org/browse/DROOLS-436.
Could someone help resolving the issue please?
#NOTE: This is an Aether internal implementation file, its format can be changed without
prior notice.
#Mon Nov 21 19:20:51 EST 2016
maven-metadata-central.xml.error=Could not transfer metadata
com.xxx.xxx.ruleengine\:fraudrules\:1.1-SNAPSHOT/maven-metadata.xml from/to central
(http\://repo1.maven.org/maven2/)\: Connect to repo1.maven.org\:80 timed out
maven-metadata-guvnor-m2-repo.xml.error=Could not transfer metadata
com.xxx.xxx.ruleengine\:rules\:1.1-SNAPSHOT/maven-metadata.xml from/to guvnor-m2-repo
(http\://10.xxx.77.xxx\:8080/kie-drools-wb/maven2/)\: Unauthorized (401)
maven-metadata-workbench.xml.lastUpdated=1479774051131
maven-metadata-guvnor-m2-repo.xml/@default-guvnor-m2-repo-http\://10.xxx.77.xxx\:8080/kie-drools-wb/maven2/.lastUpdated=1479774051096
maven-metadata-central.xml/@default-central-http\://repo1.maven.org/maven2/.lastUpdated=1479774050359