{"id":705,"date":"2019-02-19T15:11:28","date_gmt":"2019-02-19T10:41:28","guid":{"rendered":"http:\/\/www.enhisecure.com\/isecureblog\/?p=705"},"modified":"2019-02-19T15:12:26","modified_gmt":"2019-02-19T10:42:26","slug":"securing-sailpoint-deployed-on-tomcat-server","status":"publish","type":"post","link":"https:\/\/www.enhisecure.com\/isecureblog\/2019\/02\/19\/securing-sailpoint-deployed-on-tomcat-server\/","title":{"rendered":"Securing SailPoint Deployed on Tomcat Server"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Secured Socket Layer (<a href=\"https:\/\/en.wikipedia.org\/wiki\/Transport_Layer_Security\">SSL<\/a>) is a protocol which provides the secured way of communication between the client and server with the help of the certificates. When using <a href=\"https:\/\/tomcat.apache.org\/\">Apache Tomcat <\/a>as a server for the deployment of<a href=\"https:\/\/sailpoint.com\"> SailPoin<\/a>t, the data that we are dealing with is sensitive in nature. With the help of  Self Sign certificates, we can secure <a href=\"https:\/\/www.sailpoint.com\/products\/identityiq\/?elqct=Website&amp;elqchannel=OrganicDirect\">Sailpoint IdentityIQ<\/a> which is hosted on tomcat server without the need of certificate authority (<a href=\"https:\/\/en.wikipedia.org\/wiki\/Certificate_authority\">CA<\/a>).<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">1 . Creation of Self Sign Certificate<\/h4>\n\n\n\n<p class=\"has-normal-font-size wp-block-paragraph\">Step 1: Open up the command prompt<\/p>\n\n\n\n<!--more-->\n\n\n\n<p class=\"has-normal-font-size wp-block-paragraph\">Step 2 : Make sure java is installed and type the following command:<\/p>\n\n\n\n<p class=\"has-normal-font-size wp-block-paragraph\"><em><strong>keytool -genkey -alias tomcat -keyalg RSA -keystore \/path\/to\/keystore\/file\/keystore_name<\/strong><\/em><\/p>\n\n\n\n<p class=\"has-normal-font-size wp-block-paragraph\">Step 3: Enter the password. The default password for tomcat is &#8220;<em><strong>changeit<\/strong><\/em>&#8220;.<\/p>\n\n\n\n<p class=\"has-normal-font-size wp-block-paragraph\">Step 4: Enter all the details for the keystore. i.e. Name, name of OU, name of organization, city, state, country.<\/p>\n\n\n\n<p class=\"has-normal-font-size wp-block-paragraph\">Step 5:  Hit enter if you want the same password for the keystore. Then keystore will be generated in the specified location.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">2 . Configuring the Tomcat Server<\/h4>\n\n\n\n<p class=\"has-normal-font-size wp-block-paragraph\">Step 1: Navigate to CATALINA_HOME<\/p>\n\n\n\n<p class=\"has-normal-font-size wp-block-paragraph\">Step 2:  Navigate into the conf directory.<\/p>\n\n\n\n<p class=\"has-normal-font-size wp-block-paragraph\">Step 3: Open the server.xml file.<\/p>\n\n\n\n<p class=\"has-normal-font-size wp-block-paragraph\">Step 4: comment the default connector port<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><em><strong>&lt;Connector port=&#8221;8080&#8243; protocol=&#8221;HTTP\/1.1&#8243;<\/strong><\/em><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><em><strong>connectionTimeout=&#8221;200000&#8243;<\/strong><\/em><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><em><strong>redirectPort=&#8221;8443&#8243; \/&gt;<\/strong><\/em><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;-<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><em><strong>&lt;!&#8211;  <\/strong><\/em><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><em><strong>&lt;Connector port=&#8221;8080&#8243; protocol=&#8221;HTTP\/1.1&#8243; <\/strong><\/em><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><em><strong> connectionTimeout=&#8221;200000&#8243; <\/strong><\/em><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><em><strong> redirectPort=&#8221;8443&#8243; \/&gt; <\/strong><\/em><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><em><strong>&#8211;&gt;<\/strong><\/em><\/p>\n\n\n\n<p class=\"has-normal-font-size wp-block-paragraph\">Step 5: Add the following connector port to the file.<\/p>\n\n\n\n<p class=\"has-normal-font-size wp-block-paragraph\"><strong><em>&lt;Connector port=&#8221;8443&#8243; protocol=&#8221;HTTPS\/1.1&#8243; SSLEnabled=&#8221;true&#8221; maxThreads=&#8221;150&#8243; scheme=&#8221;https&#8221; secure=&#8221;true&#8221; clientAuth=&#8221;false&#8221; sslProtocol=&#8221;TLS&#8221; keystoreFile=&#8221;\/path\/to\/keystore\/file\/&#8221; keystorePass=&#8221;&lt;password&gt;&#8221; \/&gt;<\/em><\/strong><\/p>\n\n\n\n<p class=\"has-normal-font-size wp-block-paragraph\">Step 6: Save the file and start the tomcat server<\/p>\n\n\n\n<p class=\"has-normal-font-size wp-block-paragraph\">Step 7: Check the tomcat server URL<\/p>\n\n\n\n<p class=\"has-normal-font-size wp-block-paragraph\"><em><strong>https:\/\/localhost:8443\/identitiyiq<\/strong><\/em><\/p>\n\n\n\n<p class=\"has-normal-font-size wp-block-paragraph\">Note: The browser will throw the exception saying that the site is not secure, this is due to the self sign certificate which has not been signed off by the CA. You can add the exception in browser and proceed.<\/p>\n\n\n\n<p class=\"has-normal-font-size wp-block-paragraph\">The following is the detailed demo for the above steps mentioned:<\/p>\n\n\n\n<figure class=\"wp-block-embed-youtube wp-block-embed is-type-video is-provider-youtube wp-embed-aspect-16-9 wp-has-aspect-ratio\"><div class=\"wp-block-embed__wrapper\">\n<iframe loading=\"lazy\" title=\"ENH iSecure: Securing SailPoint Deployed on Tomcat Server\" width=\"640\" height=\"360\" src=\"https:\/\/www.youtube.com\/embed\/dgeDSS3uFSs?feature=oembed\" frameborder=\"0\" allow=\"accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share\" referrerpolicy=\"strict-origin-when-cross-origin\" allowfullscreen><\/iframe>\n<\/div><\/figure>\n","protected":false},"excerpt":{"rendered":"<p>Secured Socket Layer (SSL) is a protocol which provides the secured way of communication between the client and server with the help of the certificates. When using Apache Tomcat as a server for the deployment of SailPoint, the data that we are dealing with is sensitive in nature. With the help of Self Sign certificates, [&hellip;]<\/p>\n","protected":false},"author":12,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[9,8,14,16],"tags":[],"class_list":["post-705","post","type-post","status-publish","format-standard","hentry","category-cyber-security","category-identity-governance","category-sailpoint","category-technology"],"_links":{"self":[{"href":"https:\/\/www.enhisecure.com\/isecureblog\/wp-json\/wp\/v2\/posts\/705","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.enhisecure.com\/isecureblog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.enhisecure.com\/isecureblog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.enhisecure.com\/isecureblog\/wp-json\/wp\/v2\/users\/12"}],"replies":[{"embeddable":true,"href":"https:\/\/www.enhisecure.com\/isecureblog\/wp-json\/wp\/v2\/comments?post=705"}],"version-history":[{"count":22,"href":"https:\/\/www.enhisecure.com\/isecureblog\/wp-json\/wp\/v2\/posts\/705\/revisions"}],"predecessor-version":[{"id":752,"href":"https:\/\/www.enhisecure.com\/isecureblog\/wp-json\/wp\/v2\/posts\/705\/revisions\/752"}],"wp:attachment":[{"href":"https:\/\/www.enhisecure.com\/isecureblog\/wp-json\/wp\/v2\/media?parent=705"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.enhisecure.com\/isecureblog\/wp-json\/wp\/v2\/categories?post=705"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.enhisecure.com\/isecureblog\/wp-json\/wp\/v2\/tags?post=705"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}