Configuring the onboarding and content import link for secured login
On the Apache Tomcat server, if you have enabled secured login (https) for BMC Remedy Smart Reporting, you must perform the following configuration. If you do not use secured login, you can directly run the user onboarding process.
Configuration settings are lost during the upgrade. After upgrading BMC Remedy Smart Reporting, you must reconfigure the URL for secured login after the upgrade is complete.
To configure secured login
On the BMC Remedy Smart Reporting server, create a keystore file onboarding.keystore with password by running the following command to from the Java installation folder (for example, c:\Program Files\Java\jdk1.7.0_55\bin).
keytool -genkey -alias server-alias -keyalg RSA -keypass password -storepass password -keystore <temporarypath to store file>
A keystore file (for example, c:\keystore_pwd\onboarding.keystore) is created.
If the Apache Tomcat server is running, stop it.
- Move the keystore file to the SmartReporting folder below the BMC Remedy Smart Reporting installation folder.
For example, if BMC Smart Reporting is installed on C:\Reporting, move the keystore file to C:\Reporting\SmartReporting\onboarding.keystore.
- Edit the server.xml file located in the <Smart_Reporting_Install_Location>\appserver\conf folder.
Uncomment the following code in the file and update the
keystorepassvalues as per the BMC Remedy Smart Reporting server details:
<Connector port="8443" protocol="org.apache.coyote.http11.Http11Protocol" SSLEnabled="true" scheme="https" secure="true" clientAuth="false" sslProtocol="TLS" maxHttpHeaderSize="8192" maxThreads="150" minSpareThreads="25" maxSpareThreads="75" enableLookups="false" disableUploadTimeout="true" acceptCount="100" URIEncoding="UTF-8" keystoreFile="C:\Reporting\SmartReporting\onboarding.keystore" keystorePass="password" />
Edit the web.xml file located at <Smart_Reporting_Install_Location>\appserver\webapps\ROOT\WEB-INF and <Smart_Reporting_Install_Location>\SmartReporting\appserver\webapps\onboarding\WEB-INF, and add the following code:
<security-constraint> <web-resource-collection> <web-resource-name>Automatic SSL Forwarding</web-resource-name> <url-pattern>/*</url-pattern> </web-resource-collection> <user-data-constraint> <transport-guarantee> CONFIDENTIAL </transport-guarantee> </user-data-constraint> </security-constraint>
- Restart the Apache Tomcat server.