I looked at this and haven't found any simpler way to do this currently.
One remark to Emil's guide -- which is correct indeed, and works, but -- it is IMHO a "hack" and therefore most likely not something we want to encourage in a quickstart.
Anyway, to simplify/clarify Emil's description:
* the EAP cartridge on OS is different from a normal EAP installation in several ways, two of them being:
* * missing security-realms in the default configuration
* * missing add-user.sh script
I'm not sure about the reasons for that, but it can be worked around:
The user configuration files ( {{ application- \ {users,roles \ }.properties }} ) can be created locally and then pushed to EAP's configuration dir on OS, and EAP will be " told " (by creating security-realms in standalone.xml) to look for them there .
I suggest we do the following ([~sgilda]):
* document ds-auth as not runnable on OS
* optionally also document the reasons for this, as described above (maybe even the workaround, anyway?)
* maybe amend the shared DEPLOY_TO_OPENSHIFT or CREATE_USERS readme with this information
* fix ds-auth's readme, section Add an Application User, to point to the correct location (currently wrong)
|
