Bug 1018868 - Demo quickstarts/switchyard/demos/policy-security-basic missing execution instructions
Summary: Demo quickstarts/switchyard/demos/policy-security-basic missing execution ins...
Keywords:
Status: MODIFIED
Alias: None
Product: JBoss Fuse Service Works 6
Classification: JBoss
Component: Examples
Version: 6.0.0,6.0.0 GA
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: DR4
: 6.0.0,6.0.0.Alpha
Assignee: Douglas Palmer
QA Contact: Martin Vecera
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-14 14:44 UTC by Martin Vecera
Modified: 2014-10-29 03:07 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-10-14 18:47:21 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SWITCHYARD-2429 0 Minor Open Improve add-user.sh instructions for quickstarts 2014-10-28 17:03:05 UTC

Description Martin Vecera 2013-10-14 14:44:47 UTC
In quickstarts/switchyard/demos/policy-security-basic/Readme.md at step no. 4, there should be specified that the user should be created in Application domain.

Comment 1 Keith Babo 2013-10-14 18:47:21 UTC
Step 4 specifically mentions application user:

"4. Create an application user"

The question asked with bin/add-user.sh is:

"What type of user do you wish to add? 
 a) Management User (mgmt-users.properties) 
 b) Application User (application-users.properties)"

Comment 2 Martin Vecera 2013-12-21 08:04:10 UTC
You are right. However, I was going through the instruction again after some time now. I even forgot logging this bug. And I hit the same issue. For some reason this is not that obvious. From the usability point of view, I would suggest extending the instruction as follow:

"4. Create an application user (i.e. in the Application User domain)"

Please re-consider and close as needed. Thanks,
Martin

Comment 3 Keith Babo 2013-12-23 13:52:24 UTC
I don't see a harm in making the instruction more explicit, but this is definitely not a blocker for the release.


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