Space banner

   

This documentation supports the 19.11 version of Remedy Smart Reporting, which is available only to BMC Helix subscribers (SaaS).
To view an earlier version, select the version from the Product version menu of the documentation at IT Service Management Suite .

Configuring the onboarding and content import link for secured login


If you have enabled secured login (https) for Remedy Smart Reporting, you must perform the following configuration on the Apache Tomcat server. Having a secured login is optional. If you do not use secured login, you can run the user onboarding process directly .

Note

Configuration settings are lost during the upgrade. After upgrading Remedy Smart Reporting, you must reconfigure the URL for the secured login.

To configure secured login

  1. On the Remedy Smart Reporting server, create a onboarding.keystore keystore file with a password by running the following command 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.

  2. If the Apache Tomcat server is running, stop it.

  3. Move the keystore file to the SmartReporting folder below the Remedy Smart Reporting installation folder.
    For example, if BMC Smart Reporting is installed in C:\Reporting, move the keystore file to C:\Reporting\SmartReporting\onboarding.keystore.
  4. Edit the server.xml file in the RemedySmartReportingInstallLocation\appserver\conf folder.
  5. Uncomment the following code in the file and update the keystoreFile and keystorepass values per the 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" />
  6. (Optional) To automatically direct the request to https instead of http, edit the web.xml file located at RemedySmartReportingInstallLocation\appserver\webapps\ROOT\WEB-INF or RemedySmartReportingInstallLocation\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>
  7. Restart the Apache Tomcat server.
Was this page helpful? Yes No Submitting... Thank you

Comments