Bug 779983 (SOA-2343)

Summary: Consoles does not support Single Sign On
Product: [JBoss] JBoss Enterprise SOA Platform 5 Reporter: Martin Vecera <mvecera>
Component: Release Process, Build Process, Configuration, SecurityAssignee: trev <tkirby>
Status: CLOSED WONTFIX QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 5.1.0.ER1   
Target Milestone: ---   
Target Release: FUTURE   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-2343
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-06 22:01:30 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:

Description Martin Vecera 2010-09-24 09:40:03 UTC
project_key: SOA

As per SOA-MMA-10 request, all consoles should support Single Sign On, which is not true currently.

Comment 3 Julian Coleman 2010-10-05 11:12:13 UTC
Note, that the configuration for single sign-on is documented in the section 22.4 of the
EAP Administation and Configuration guide:

  http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5/html/Administration_And_Configuration_Guide/clustering-http-sso.html

along with its limitiations (for example, *all* applications on the virtual host share the same authentication).

Note, also, that the admin console doesn't use the single sign-on credentials (see JBPAPP-5191).

Comment 4 Julian Coleman 2010-10-05 11:13:10 UTC
Link: Added: This issue is related to JBPAPP-5191


Comment 5 Kevin Conner 2010-11-01 16:04:05 UTC
Given that this affects all applications on the same virtual host it would be better to create a separate host for the consoles.  I'm not sure if either route is desirable by default though, at least not at this stage.

Comment 7 Anne-Louise Tangring 2010-12-02 15:26:43 UTC
PM team decided this is not a blocker for 5.1.0. This should be strongly considered and discussed for SOA 5.2.0