Oracle Wallet manager error

Question

Hi all,
Inorder to test SSL, i created a certificate request in OWM.Then i got a trial certificate from verisign for this request.What should i do now ? I tried to import that certificate in Oracle Wallet manager but getting this error.
"Trusted Certificate Installation Failed.
Input was not a valid certificate".
Please guide me
Srini

Answer 1

belw is the note
PURPOSE
To list the steps needed to configure Oracle HTTP Server (OHS) to use the Secure
Sockets Layer (SSL) when installed with Oracle9i Application Server (9iAS)
Release 2 (9.0.2). The below instructions show, step by step, instructions for
obtaining a trial certificate from a Certificate Authority, such as Verisign or
Thawte. Please refer to the Oracle 9iAS Documentation for further details.
SCOPE AND APPLICATION
Oracle9i Application Server (9iAS) Release 2 (9.0.2 and above)
Configuring SSL with Oracle HTTP Server in 9iAS Release 2
There are two major steps needed to configure SSL in 9iAS:
I. Create an Oracle Wallet which contains an SSL Certificate
II. Configure httpd.conf directives to enable SSL with OHS
NOTE:
Only standard server certificates are supported. These are sometimes referred
to as "40-bit Certificates", but will allow 128-bit encryption provided the
browser supports 128-bit encryption. 9iAS Release 2 does not support Global
Server Certificates, called "128-bit Certificates", that allow 56-bit export
browsers to step up to 128-bit.
STEP I: Configuring Oracle Wallet Manager (OWM)
1. Start Oracle Wallet Manager from the 9iAS $ORACLE_HOME.
Note: If you wish to use AutoLogin features you must start OWM as the user
who owns the httpd parent process.
To start Oracle Wallet Manager:
On Windows: select Start > Programs > Oracle - ORACLE_HOME >
Integrated Management Tools > Wallet Manager
On UNIX: enter owm at the command line.
2. Create an Oracle Wallet which contains an SSL Certificate:
- Select Wallet -> New
- Enter a password for the wallet e.g Welcome1
- Create a Certificate Request.
- Enter the details for the request. For example:
     Common Name:          <hostname.domainname>
Organizational Unit:      Support
Organization:      Oracle
     Location:          Reading
     State:               Berkshire
     Country:          United Kingdom
     Key Size:          1024bits
* Common Name has to match the hostname.domainname that the webserver is
known as. This is the Servername parameter in the httpd.conf file, and
is the hostname.domainname that users will enter in the browser URL.
- Click OK.
- Click 'Certificate:[Requested]' and select from the Menu 'Operations' and
'Export Certificate Request'
- Save to a file e.g server.csr
- Open the file in a text editor and copy the contents of the certificate
signing request, to be pasted in a Certificate Authority (Verisign) form.
An example is shown below:
-----BEGIN NEW CERTIFICATE REQUEST-----
MIIBtzCCASACAQAwdzELMAkGA1UEBhMCR0IxEjAQBgNVBAgTCWJlcmtzaGlyZTEQMA4GA1UEBxMH
cmVhZGluZzEPMA0GA1UEChQGb3JhY2xlMRAwDgYDVQQLFAdzdXBwb3J0MR8wHQYDVQQDFBZ1a2Ro
MTkzNC51ay5vcmFjbGUuY29tMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCYkFMb9x4ehsG3
yQ2ub319GxPW+/TC3NSIYRLzEa49EziqBUr08R3Ssn9+6nolVjj1eb3rzwCfjiOSzsp1lSa/B9Vo
63pwP6xLbCgF8J86YfcZvavgLzY0Yc1fPfRxpZkb/jjt+F1zkaI6Lilm5YU3bRNYMb36TAWxUYL1
m6wZOwIDAQABoAAwDQYJKoZIhvcNAQEEBQADgYEACKXTmPHaSe3Lx3onnKJk/qI8SzpKyQC/B29v
JGg1+7Lb7gl052Y9WKxbKHzOQOYr8yYxMXNBCUwW6kBAFoxTWSpIxIQOpJXcsu1RlHKaLfAnw053
LiwpRB6do7MBrVgMRiv3AyTkJkgRzSxABWAgNpBPbhH+L6PZj5tSjOPErKA=
-----END NEW CERTIFICATE REQUEST-----
3. Request a Certificate from a Certificate Authority:
- Load a web browser and go a Certificate Authority website of your choice.
The examples below are from www.thawte.com:
- Click on 'request your free trial'.
- Fill in the necessary name and address details etc. and 'Submit'.
- Paste in the certificate request into the box under the
'Certificate Signing Request' Section.
- Select "Test X509v3 SSL Cert" and hit "Generate Test Certificate"
- Once submitted the Trial Certificate will appear on screen similar to below:
-----BEGIN CERTIFICATE-----
MIICnDCCAgWgAwIBAgIDD9m+MA0GCSqGSIb3DQEBBAUAMIGHMQswCQYDVQQGEwJa
QTEiMCAGA1UECBMZRk9SIFRFU1RJTkcgUFVSUE9TRVMgT05MWTEdMBsGA1UEChMU
VGhhd3RlIENlcnRpZmljYXRpb24xFzAVBgNVBAsTDlRFU1QgVEVTVCBURVNUMRww
GgYDVQQDExNUaGF3dGUgVGVzdCBDQSBSb290MB4XDTAxMTAyNDE0MDIxOVoXDTAx
MTExNDE0MDIxOVowdzELMAkGA1UEBhMCR0IxEjAQBgNVBAgTCUJlcmtzaGlyZTEQ
MA4GA1UEBxMHUmVhZGluZzEPMA0GA1UEChQGT3JhY2xlMRAwDgYDVQQLFAdTdXBw
b3J0MR8wHQYDVQQDFBZ1a3AxNTkxOC51ay5vcmFjbGUuY29tMIGfMA0GCSqGSIb3
DQEBAQUAA4GNADCBiQKBgQDiQbg8KHjQ8hazvFe+OFhQa6ka+i5oShUty1MhlH+/
/xXP+j82h4VlyPG6IGKeQdXLhnKXgLuxTZ8/VDtLZyucmpIB95o2A3Betjp7UdIm
C572rKrQTA+1mCt/KLWcNE+fQuCmhloaERh3jsWTng0TKsDpJeAJdW2F4tCy/E/E
MwIDAQABoyUwIzATBgNVHSUEDDAKBggrBgEFBQcDATAMBgNVHRMBAf8EAjAAMA0G
CSqGSIb3DQEBBAUAA4GBACffzyC3qvAlvNWc6mBPMjFu6XWUGZBuNawFCz8qGw5/
ce3rWFNI4zOjc1OncoJg7FjDJgAWqiJFHgdV4gwQm/8lTJX6wD1FhMtrJDXf29ei
1DAe8kBOBWiFMio8Qjp24TdxoI6/53/32ydl91CPtTKAix3SaC2bBS5lG73AbKRr
-----END CERTIFICATE-----
- Copy the certificate to a file called server.crt
- Get the Trusted CA Root certificate by accessing:
https://www.thawte.com/roots/index.html
- Copy the certificate that appears on the screen to a file called
servertest.crt
- Ftp or move the files to a directory on your server
- In Wallet Manager select Operations -> Import User Certificate.
- It will then ask you if you want to Paste the certificate or load
from a file. Choose 'Select a file that contains a certificate'.
- Select the file server.crt and hit OK.
- At this point, the Wallet Manager may complain that the Trusted CA Root
Certificate does not exist in the wallet. It will ask if you want to
import it now. Select Yes. See Below
- Select 'Select a file that contains a certificate' and select the
servertest.crt file.
- If this completes successfully you should see Certificate:[Ready] and the
Thawte Test CA Root will appear in the list of trusted certificates.
- If you desire Oracle HTTP Server to AutoLogin to the Wallet, then select
AutoLogin. (Wallet Manager must have been started as the owner of the
httpd parent process for this to work).
- From the menu, File -> Save
Save the Wallet in a directory where the 9iAS user has permission to access
* If you generated your test certificate via www.verisign.com there is an additional
step required if OWM is not accepting the Trusted CA Root Certificate. The step is
as follows:
In OWM, at the point of message "User certificate import has failed because the
CA certificate does not exist". You are expected to import the CA certificate.
For Verisign, that would be the 'Test CA Root' for the Trial version. Verisign's
email has instructions on how to download the Test CA Root. One problem with the
Test CA Root is that it is saved as DER encoding, but OWM expects BASE64 encoding.
Please do following, using Internet Explorer 5.X as example.
1. Following Verisign instructions and install Test CA Root
certification into IE.
2. Export 'Test CA Root' from IE in BASE64 format
Tools -> Internet Options -> Contents -> Certificates
-> Trusted Root Certificate Authorities
Select CA issued by Versign with following Description in 'Issued to' column
"For Versign authorized testing only ....."
Export -> Next -> select Base-64 encoded X.509(.cer)
The file saved must me accessible to OWM
3. When prompted to load 'CA certificate ', provide the Base64 encoded file.
Then, continue where you left off when OWM did not accept your Trusted CA
Root Certificate.
STEP II: Configuring Oracle HTTP Server (OHS)
Please review the default directives in the httpd.conf file that relate to SSL by
opening the file in a text editor and search on "SSL". If you have not already
done so, please make a back up of this file. Do NOT hand edit this file without reading
the precautions in the 9iAS Documentation. You should use the Enterprise Manager (EM)
Website to modify this file. For SSL to work, the SSL 'listen' port must match the
"VirtualHost _default_" directive within the file. All other SSL parameters are
set to the default, and you can modify at a later time, depending on your needs.
## SSL Support
Listen 80
Listen 443
#443 is the SSL port number.
##Further down in file:
<VirtualHost default:443>
For the purposes of a basic SSL configuration, you should only need to
change the following directives:
SSLWallet
SSLWalletPassword
- Change the SSLWallet directive to the path where you saved your wallet, i.e:
SSLWallet file:/tmp/wallets
- If you get an error, ADMN-906025 with exception 806212, when starting OHS
after modifying httpd.conf, it is because you need to supply this password.
You may also see errors such as the following:
Error Failed to restart HTTP Server.
Timeout has been reached. Timeout has been reached.
If you did not select AutoLogin, then you need to change the SSLWalletPassword
to your clear text Wallet password by adding the following into your httpd.conf
SSLWalletPassword <yourPassword>
- If you wish to encrypt the SSLWalletPassword refer to the following:
[NOTE:184677.1]
How to Use IASOBF to Encrpyt a Wallet Password Within 9iAS Release 2
- Save the configuration, and restart Oracle HTTP Server
- Test a URL to Oracle HTTP Server in SSL mode:
https://<hostname.domainname>:<port>