Bug 779983 (SOA-2343) - Consoles does not support Single Sign On
Summary: Consoles does not support Single Sign On
Keywords:
Status: CLOSED WONTFIX
Alias: SOA-2343
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: Release Process, Build Process, Configuration, Security
Version: 5.1.0.ER1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: FUTURE
Assignee: trev
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-24 09:40 UTC by Martin Vecera
Modified: 2011-12-06 22:01 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-06 22:01:30 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-2343 0 None None None Never

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
Note You need to log in before you can comment on or make changes to this bug.