Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1313124

Summary: Unauthorized (401) when deploying artifact with encrypted server and master passwords
Product: [Retired] JBoss BPMS Platform 6 Reporter: Hiroko Miura <hmiura>
Component: Business CentralAssignee: manstis
Status: CLOSED EOL QA Contact: Lukáš Petrovický <lpetrovi>
Severity: high Docs Contact:
Priority: high    
Version: 6.2.0CC: manstis
Target Milestone: ER1   
Target Release: 6.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1313125 (view as bug list) Environment:
Last Closed: 2020-03-27 19:36:29 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1313125    

Description Hiroko Miura 2016-03-01 02:12:40 UTC
Description of problem:

The project is configured to deploy artifacts to a remote nexus repository. Distribution management is set up in project poms.
The jboss user's ~/.m2/settings.xml is configured with matching repo id, username, and encrypted password. The master password is configured in ~/.m2/settings-security.xml. When a kjar is built, the build fails with a 401 unauthorized error, and artifacts are not published to remote nexus.

This issue has already been fixed in the upstream via this JIRA 

https://issues.jboss.org/browse/GUVNOR-2279 

Kindly fix the same issue for our future versions of BRMS/BPMS 6 releases too.



Version-Release number of selected component (if applicable):
6.2.0


How reproducible:
-always 


Steps to Reproduce:
1. configure B*MS6.2.0  project to deploy artifacts to a remote nexus repository by pom.xml in Business Central.

2. encrypt password of remote repository in settings.xml by settings-security.xml
 
   Ref: https://maven.apache.org/guides/mini/guide-encryption.html

3. perform Build&Deploy the project


Actual results:
Deployment fails with error 401.

Expected results:
Deployment succeed.

Additional info:

Comment 2 Pavel Kralik 2016-03-24 13:13:57 UTC
BPMS 6.3.0.ER1 - deployment fails with error 401 in Business central.
RHEL7/EAP6.4

Comment 4 Pavel Kralik 2016-03-30 16:24:25 UTC
BPMS 6.3.0.ER2 verified with example from GUVNOR-2279.