Bug 1010780 - Enable SSO by default between Dashbuilder and Business Central applications
Summary: Enable SSO by default between Dashbuilder and Business Central applications
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: Build and Assembly
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ER4
: 6.0.0
Assignee: Julian Coleman
QA Contact: Jan Hrcek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-23 05:03 UTC by Jan Hrcek
Modified: 2014-08-06 20:06 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-08-06 20:06:11 UTC
Type: Bug


Attachments (Terms of Use)
double login needed when SSO not enabled (286.11 KB, image/png)
2013-09-23 05:03 UTC, Jan Hrcek
no flags Details

Description Jan Hrcek 2013-09-23 05:03:16 UTC
Created attachment 801490 [details]
double login needed when SSO not enabled

Description of problem:
When using Dashbuilder features, that are built into business central UI, it is necessary to login twice. See screenshot attached to see what I mean. It is possible to enable SSO (Single Sign-On) between Dashbuilder and Business Central using EAP config file(s) standalone.xml etc.

The configuration step needed is described in the dashbuilder (jbpm-dashboard) readme file here: https://github.com/droolsjbpm/jbpm-dashboard/blob/master/jbpm-dashboard-distributions/src/main/jbossas7/README.md#single-sign-on

Please enable SSO as described in the README above, by adding the <sso /> element in the EAP configuration files (standalone.xml, standalone-full.xml etc.), so that the duplicate login is not needed.

Comment 1 Rajesh Rajasekaran 2013-10-14 20:10:45 UTC
This should be fixed in the ER4 build. Marking it as MODIFIED.

Comment 2 Jan Hrcek 2013-10-15 04:40:39 UTC
This fix is present in ER4. Changing to ON_QA. Will verify as soon as the ER4 build is accepted.

Comment 3 Jan Hrcek 2013-10-16 13:17:02 UTC
Ok, verified with BPMS 6.0.0 ER4


Note You need to log in before you can comment on or make changes to this bug.