Description of problem: Add-user utility gives us the ability to specify properties files which should be used to store users. However error is thrown once user tries to use properties file that doesn't exist. If this is a desired behaviour we may explicitly mention this in add-user script help message. Version-Release number of selected component (if applicable): EAP 6.2.0.ER6 How reproducible: always Steps to Reproduce: 1. Navigate into $EAP_HOME/bin folder 2. Run: jboss-eap-6.2/bin]$ ./add-user.sh -u appuser1 -p password1! -up appusers.properties Actual results: * Error * JBAS015234: No appusers.properties files found. Expected results: Properties file is created. Additional info: If there is a good reason for not creating the properties file we should at least mention this in script help message and documentation (BZ872441). Example 4.4. Create a user belonging to single group using alternate properties files to store the information. http://documentation-devel.engineering.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/6.2/html-single/Administration_and_Configuration_Guide/index.html#Add-user_Script_Command_Line_Examples
Please let me know if the plans are to fix this. As Petr said, if there are no plans to create the file if it doesn't exist, I need to document it.
Does anyone have an update on this issue? I need to know ASAP if I need to document this in the Administration and Configuration Guide (https://bugzilla.redhat.com/show_bug.cgi?id=872441).
No plans to look into this for EAP 6.2. Better error messages may be appropriate in a future release but the intention of add-user is to be adding users to the property files already in use by the server i.e. we do expect them to exist.
I am NACKing this on the basis that creation of property files is not an intended function of add-user When the properties file name is specified add-user searches known locations for the file and outputs the error reported here if the file is not found in any of those locations. At this point add-user does not know which of the locations it should even create the file in, the error message also potentially means there is an un-startable server as there is likely also a server referencing files that do not exist.
The behaviour of add user was documented as part of BZ872441 so I believe we can close this one.