Description of problem: It's difficult for users to use the s-ramp demos now that there is no default admin password. For all demos that use maven, the user must create a settings.xml file and store the credentials there. Also, when using the CLI the connect command requires the credentials to be stored in the commands file just like any other command argument. How reproducible: Always Steps to Reproduce: 1. Install s-ramp/dtgov 2. Try any maven based demo 3. Try using the CLI in batch mode (with a commands file) Actual results: Failure to authenticate to s-ramp. User must supply a settings.xml file when using maven. User must modify the CLI commands file when using the CLI in batch mode. Expected results: Prompt the user for credentials if not provided. Additional info: The user should be prompted for the s-ramp username/password if not supplied (via settings.xml for maven or via the CLI commands file for the CLI).
Until this BZ is resolved, users can provide credentials to maven builds via a settings.xml file. Some documentation has been added to the s-ramp demos here: https://github.com/Governance/s-ramp/pull/333/files For the CLI, users must supply credentials on the argument list for the connect command.
The CLI and the Maven integration have both been changed so that they will now prompt the user for a username/password if not provided. For the CLI, the credentials can be provided in the commands file as arguments to the 'connect' command. For the Maven integration, credentials must be provided in a settings.xml file as required by Maven. Again, if not provided in the above ways, each will now prompt the user to enter them. This should make manually running the CLI in batch mode easier. It should also make running the s-ramp and dtgov Maven related quickstarts easier. Note that for non-Maven related s-ramp quickstarts the credentials can be provided on the command line (no change from Beta).
Verified in FSW 6.0.0.ER8