The problem I was facing was of CAS implementation. I had to test the implementation in my local environment. The CAS implementation is such that it will require HTTPS protocol to work properly. So I have to configure my tomcat for SSL.
How Certificate works
The steps you should follow to configure a Security certificate to your tomcat are as follows.
1. To create a new keystore from scratch, containing a single self-signed Certificate, execute the following from a terminal command line:
2. To create a CSR as follows
3. OR (export the generated certificate to a file)
4. To create the trust store file cacerts.jks and add the certificate to the truststore
- to add the certificate to the trust of java
How Certificate works
- First the server needs a private key which it keeps itself
- Then it generates the certificate(which also contains the public key, i think)
- on first page request, server sends certificate(user has to accept and trust it if it is not signed by trusted associations)
- Then a SSL handshake is made (server has private key and the user has the public key, each can decrypt others message)
- REF: http://security.stackexchange.com/questions/20803/how-does-ssl-tls-work
The steps you should follow to configure a Security certificate to your tomcat are as follows.
- Create a self signed certificate(keystore, eg common.jks)
- Create a certificate file from the keystore(eg. common.cer).
- Add the certificate to the trust store of java.
1. To create a new keystore from scratch, containing a single self-signed Certificate, execute the following from a terminal command line:
"%JAVA_HOME%\bin\keytool" -genkey -alias tomcat -keyalg RSA -keystore D:\Tomcats\common.jks
Note: creates file named abc.jks/*
2. To create a CSR as follows
"%JAVA_HOME%\bin\keytool" -keystore "D:\Tomcats\common.jks" -certreq -alias tomcat -keyalg rsa -file "D:\Tomcats\common.csr"*/
3. OR (export the generated certificate to a file)
"%JAVA_HOME%\bin\keytool" -export -alias tomcat -storepass changeit -file "D:\Tomcats\common.cer" -keystore "D:\Tomcats\common.jks"
4. To create the trust store file cacerts.jks and add the certificate to the truststore
"%JAVA_HOME%\bin\keytool" -import -v -trustcacerts -alias tomcat -file "D:\Tomcats\common.cer" -keystore "D:\Tomcats\cacerts.jks" -keypass changeit
- to add the certificate to the trust of java
"%JAVA_HOME%\bin\keytool" -import -alias tomcat -file "D:\Tomcats\common.cer" -keystore "%JAVA_HOME%\jre\lib\security\cacerts"5. Delete an already present certificate
keytool -delete -alias tomcat -keystore "D:\Tomcats\common.jks" -storepass changeit
After the certificate stuff, you have to configure the <tomcat-home>/conf/server.xml to use the certificate just generated. Its optional to keep or comment out the http port but its better to comment it out because allowing both https port and http port would slow down your application and consume more resources.
<?xml version='1.0' encoding='utf-8'?>
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
The ASF licenses this file to You under the Apache License, Version 2.0
(the "License"); you may not use this file except in compliance with
the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
<!-- Note: A "Server" is not itself a "Container", so you may not
define subcomponents such as "Valves" at this level.
Documentation at /docs/config/server.html
-->
<Server port="1005" shutdown="SHUTDOWN">
<!-- Security listener. Documentation at /docs/config/listeners.html
<Listener className="org.apache.catalina.security.SecurityListener" />
-->
<!--APR library loader. Documentation at /docs/apr.html , commented by rajan-->
<!--<Listener className="org.apache.catalina.core.AprLifecycleListener" SSLEngine="on" />-->
<!--Initialize Jasper prior to webapps are loaded. Documentation at /docs/jasper-howto.html -->
<Listener className="org.apache.catalina.core.JasperListener" />
<!-- Prevent memory leaks due to use of particular java/javax APIs-->
<Listener className="org.apache.catalina.core.JreMemoryLeakPreventionListener" />
<Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener" />
<Listener className="org.apache.catalina.core.ThreadLocalLeakPreventionListener" />
<!-- Global JNDI resources
Documentation at /docs/jndi-resources-howto.html
-->
<GlobalNamingResources>
<!-- Editable user database that can also be used by
UserDatabaseRealm to authenticate users
-->
<Resource name="UserDatabase" auth="Container"
type="org.apache.catalina.UserDatabase"
description="User database that can be updated and saved"
factory="org.apache.catalina.users.MemoryUserDatabaseFactory"
pathname="conf/tomcat-users.xml" />
</GlobalNamingResources>
<!-- A "Service" is a collection of one or more "Connectors" that share
a single "Container" Note: A "Service" is not itself a "Container",
so you may not define subcomponents such as "Valves" at this level.
Documentation at /docs/config/service.html
-->
<Service name="Catalina">
<!--The connectors can use a shared executor, you can define one or more named thread pools-->
<!--
<Executor name="tomcatThreadPool" namePrefix="catalina-exec-"
maxThreads="150" minSpareThreads="4"/>
-->
<!-- A "Connector" represents an endpoint by which requests are received
and responses are returned. Documentation at :
Java HTTP Connector: /docs/config/http.html (blocking & non-blocking)
Java AJP Connector: /docs/config/ajp.html
APR (HTTP/AJP) Connector: /docs/apr.html
Define a non-SSL HTTP/1.1 Connector on port 8080
-->
<!-- <Connector port="1111" protocol="HTTP/1.1"
connectionTimeout="20000"
redirectPort="1443" />
-->
<!-- A "Connector" using the shared thread pool-->
<!--
<Connector executor="tomcatThreadPool"
port="8080" protocol="HTTP/1.1"
connectionTimeout="20000"
redirectPort="8443" />
-->
<!-- Define a SSL HTTP/1.1 Connector on port 8443
This connector uses the JSSE configuration, when using APR, the
connector should be using the OpenSSL style configuration
described in the APR documentation -->
<!--
<Connector port="8443" protocol="HTTP/1.1" SSLEnabled="true"
maxThreads="150" scheme="https" secure="true"
clientAuth="false" sslProtocol="TLS" />
-->
<!--<Connector port="1443" maxThreads="150" scheme="https"
secure="true" SSLEnabled="true" keystoreFile="conf/ssoServer.jks"
keystorePass="changeit" clientAuth="false" keyAlias="tomcat"
sslProtocol="TLS"/>
-->
<Connector port="1443" maxThreads="150" scheme="https"
secure="true" SSLEnabled="true" keystoreFile="D:/Tomcat/common.jks"
keystorePass="changeit" clientAuth="false" keyAlias="tomcat" sslProtocol="TLS"/>
<!-- Define an AJP 1.3 Connector on port 8009 -->
<Connector port="1009" protocol="AJP/1.3" redirectPort="1443" />
<!-- An Engine represents the entry point (within Catalina) that processes
every request. The Engine implementation for Tomcat stand alone
analyzes the HTTP headers included with the request, and passes them
on to the appropriate Host (virtual host).
Documentation at /docs/config/engine.html -->
<!-- You should set jvmRoute to support load-balancing via AJP ie :
<Engine name="Catalina" defaultHost="localhost" jvmRoute="jvm1">
-->
<Engine name="Catalina" defaultHost="localhost">
<!--For clustering, please take a look at documentation at:
/docs/cluster-howto.html (simple how to)
/docs/config/cluster.html (reference documentation) -->
<!--
<Cluster className="org.apache.catalina.ha.tcp.SimpleTcpCluster"/>
-->
<!-- Use the LockOutRealm to prevent attempts to guess user passwords
via a brute-force attack -->
<Realm className="org.apache.catalina.realm.LockOutRealm">
<!-- This Realm uses the UserDatabase configured in the global JNDI
resources under the key "UserDatabase". Any edits
that are performed against this UserDatabase are immediately
available for use by the Realm. -->
<Realm className="org.apache.catalina.realm.UserDatabaseRealm"
resourceName="UserDatabase"/>
</Realm>
<Host name="localhost" appBase="webapps"
unpackWARs="true" autoDeploy="true">
<!-- SingleSignOn valve, share authentication between web applications
Documentation at: /docs/config/valve.html -->
<!--
<Valve className="org.apache.catalina.authenticator.SingleSignOn" />
-->
<!-- Access log processes all example.
Documentation at: /docs/config/valve.html
Note: The pattern used is equivalent to using pattern="common" -->
<Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs"
prefix="localhost_access_log." suffix=".txt"
pattern="%h %l %u %t "%r" %s %b" />
</Host>
</Engine>
</Service>
</Server>
No comments:
Post a Comment
If you like to say anything (good/bad), Please do not hesitate...