Bug 724108 (BRMS-51) - We need to explicitly document how users must configure identity and user accounts for OOTB configuration
Summary: We need to explicitly document how users must configure identity and user acc...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: BRMS-51
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: Documentation
Version: 5.0.0 EA1
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: ---
: 5.0.0.CR2
Assignee: Dana Mison
QA Contact:
URL: http://jira.jboss.org/jira/browse/BRM...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-02-11 16:00 UTC by Len DiMaggio
Modified: 2010-03-02 18:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-03-02 18:10:18 UTC
Type: Task

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


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

Description Len DiMaggio 2009-02-11 16:00:06 UTC 
Affects: Documentation (Ref Guide, User Guide, etc.)
Date of First Response: 2009-04-27 21:07:51

We need to explicitly document how users must configure identity and user accounts for OOTB configuration.

After installing, the user must:
** Set up container to talk to identity DB (LDAP, JAAS, etc.)
** Define user accounts within user roles defined in BRMS

This is not configured by default.
Comment 1 Dana Mison 2009-04-28 01:07:51 UTC 
added generic instructions with a simple example of file based authentication like the default soa authentication (brms-users.properties)

TODO: more detailed example using LDAP (need to setup fedora directory server to test)
Comment 2 Dana Mison 2009-04-28 01:08:44 UTC 
Also TODO: user role setup
Comment 3 Dana Mison 2009-05-13 05:03:41 UTC 
configuration information and examples have been added to the BRMS user guide.
Comment 4 Len DiMaggio 2010-03-02 18:10:18 UTC 
Verified in the 5.0.1 user guide.
Note You need to log in before you can comment on or make changes to this bug.