> On Jun 18, 2015, at 9:07 AM, Shawn McKinney <[email protected]> wrote: > > that tells it which port to listen to, which protocol, location of keystone > and its password. > > The client-side has to know the new URL, the location of the truststore that > contains the public key. Are you using the fortress-core as the test client? > If so you will need to change some fortress properties to match the new > server coordinates.
If using fortress-core client program to test your fortress-rest server, add these params to build.properties file (in fortress-core project) and rerun the ‘mvn install’ target. enable.mgr.impl.rest=true # test user account: http.user=demouser4 http.pw=password http.host=localhost http.port=8443 http.protocol=https The http.user is usually added via a script and has the roles necessary to hit the fortress-rest server (nothing has changed here) The http.port will need to point to whatever TLS port you chose in Tomcat. The http.protocol is used to construct the necessary path for TLS enablement. finally you will need to tell the fortress-core runtime (client-side) where the trust store is that contains the public key to your Tomcat server: trust.store=/fully/qualified/file/name/to/mytruststore trust.store.password=changeit trust.store.set.prop=true Shawn [email protected]
