Bug 836369 - Custom properties files cannot be managed by add_user script
Summary: Custom properties files cannot be managed by add_user script
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Documentation
Version: 6.0.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: EAP 6.0.1
Assignee: Misty Stanley-Jones
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-06-28 20:35 UTC by Travis Rogers
Modified: 2014-06-18 07:04 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Instance Name: Not Defined Build: CSProcessor Builder Version 1.5 Build Filter: null Build Name: Build Date: 20-06-2012 22:01:18
Last Closed: 2013-03-21 01:57:37 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Travis Rogers 2012-06-28 20:35:33 UTC
JBoss EAP 6 documentation for security realms [1] should clarify that user created properties files are not managed by the add_user script or remove references that mention a user created properties file.

List item 3 references a user supplied myfile.properties.

3. Create the references to the properties file which will store information about the new role.
Run the following command to create a pointer a file named myfile.properties, which will contain the properties pertaining to the new role.

/host=master/core-service=management/security-realm=MyDomainRealm/authentication=properties:add(path=myfile.properties)


The Result section also mentions this file.

Result
Your new security realm is created. When you add users and roles to this new realm, the information will be stored in a separate file from the default security realms.



[1] http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/6/html/Development_Guide/Add_a_New_Security_Realm.html

Comment 1 Misty Stanley-Jones 2012-07-03 02:05:25 UTC
Added the following note in the relevant step:

The newly-created properties file is not managed by the included <filename>add-user.sh</filename> and <filename>add-user.bat</filename> scripts. It must be managed externally.

Also added the following sentence at the end of the Result:


You can manage this new file using your own applications or procedures.


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