THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
This realm type allows you to configure Web applications to authenticate users against it. To get to that point, you will need to first configure Geronimo to use a custom SSL port listener and to get to that point you will need to configure SSL keys and keystore. The following sections describe step-by-step how to configure each of these modules.
...
This is a PKCS10 certification request, you should copy this text and paste it into a flat txt file so it can be sent to a CA.
...
You can now click Back to return to the private key details portlet.
For this example we used a custom, home made CA so we could sign our own certificates for this test without altering the standard procedure. Assuming that you sent you CSR to a CA, the CA should respond back with another similar file containing the CA signed certificate.
...
...
From the private key details portlet click on Import CA reply. Remove any pre-filled text in the certificate reply window and paste the text from the CA reply file and click on Save.
...
In order to enable client authentication you will need to import the CA who signed your CSR as a trusted certificate, this process has to be only once. The CA should provide along with the signed CSR a separate certificate for the CA itself. For this example we are using our own CA so we generated the following CA certificate.
...
While in the Keystore Configuration portlet click on the keystore file you created and then click on Add Trust Certificate. Delete any pre-filled content from Trusted Certificate window and paste the content from the CA certificate and add an alias to this certificate.
...
The properties files should be based on the client certificate intended to be used for client authentication. For example, a Certificate Properties File Realm CertificatePropsRealm with the user and group properties files based on My_Private_key created in the #Create keystore and certificate section is as follows:
...
...
- The password of
client1is based on the information ofMy_Private_key.
...
...
The deployment plan of the Certificate Properties File Realm CertificatePropsRealm is as follows:
...
...
where
<moduleId> .. </moduleId>: is the tag that defines the module ID of the security realm. This attribute is included Applications which use this security realm for authentication should include this attribute as a dependency in the deployment plan of any application that uses this security realm to authenticate clients.<attribute name="realmName">CertificatePropsRealm</attribute>:CertificatePropsRealmis the name of the security realm.
Configure the deployment descriptor and deployment plan of your web application to use the Certificate Properties File Realm for client authentication. For example, applications which use the CertificatePropsRealm security realm must configure their The deployment descriptor is configured as follows:
...
...
where
<auth-method>CLIENT-CERT</auth-method>: suggests that the auth-method is set toCLIENT-CERTand thus, uses client certificate for authentication.CLIENT-CERTis often used for SSL mutual authentication. In Geronimo, such configuration suggests that a Certificate Properties File Realm is used for authentication with a client certificate.
The deployment plan is configured Web applications which use the CertificatePropsRealm security realm, for example, must configure their deployment plans as follows:
...
...
where
<security-realm-name>CertificatePropsRealm</security-realm-name>:CertificatePropsRealmis the Certificate Properties File Realm used for client authentication.<sys:dependency> .. </sys:dependency>:elements in this tag identify the module ID of the Certificate Properties File Realm used for authentication.
...