]
Alejandro Guizar resolved JBPM-2656.
------------------------------------
Labels: configuration jbpm3 security_domain service web (was: )
Assignee: Alejandro Guizar
Resolution: Out of Date
Already in sync:
Service:
JAAS configuration within jBPM 3.2.8 not in sync
------------------------------------------------
Key: JBPM-2656
URL:
https://jira.jboss.org/browse/JBPM-2656
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 3.2.8
Reporter: MohReece
Assignee: Alejandro Guizar
Labels: security_domain, configuration, service, web, jbpm3
In the jboss-service.xml file (from the
/deploy/server/default/deploy/jbpm/jbpm-service.sar/META-INF/ directory) the name
attribute of the jaas:application-policy tag is set to 'jbpm-console'.
In the jboss-web.xml (from the
/deploy/server/default/deploy/jbpm/jsf-console.war/WEB-INF/ directory) the value for the
security-domain tag is set to 'java:/jaas/soa'.
This means that when the contents of the /deploy/ directory are copied as-is to an
appropriate directory on an application server (as tested on JBoss EAP 4.3) it will not be
possible to log in at the jBPM console.
It is simply solved by synching these two values (e.g. set the jaas:application-policy
tag name attribute to 'soa').
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: