Bug 669476
Summary: | Principal and credentials can not be auto-discovered for SOA-P instance due to wrong user and role properties file name | ||
---|---|---|---|
Product: | [Other] RHQ Project | Reporter: | Larry O'Leary <loleary> |
Component: | Plugins | Assignee: | Nobody <nobody> |
Status: | NEW --- | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 3.0.0 | CC: | jshaughn, loleary |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: |
JON 2.4
SOA-P 5
|
|
Last Closed: | Type: | --- | |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Larry O'Leary
2011-01-13 18:49:50 UTC
After more thought, it appears that the plug-in is actually looking things up incorrectly. For AS plug-in, if we are using JMX, then we should be looking up the securityDomain in jmx-invoker-service.xml (like we are) and then getting the path to the users/roles property files from login-config.xml using the application policy which matches the security domain. For AS5 plug-in, we would do the same as the AS plug-in if we are needing JMX but seeing that we are using ProfileService, we should be looking up the securityDomain in profileservice-jboss-beans.xml and then getting the users/roles property files from login-config.xml. Then, we could try 2, 3, and default to 4 if all else fails. Keeping in mind that this will not work in every instance but would be broadening the success in many use-cases and lower the impact of future changes/platforms breaking the ability for auto-discovery to get a hold of a valid user/password. |