| Oracle® Database Advanced Security Administrator's Guide 11g Release 2 (11.2) Part Number E10746-02 |
|
|
PDF · Mobi · ePub |
| Oracle® Database Advanced Security Administrator's Guide 11g Release 2 (11.2) Part Number E10746-02 |
|
|
PDF · Mobi · ePub |
Security administrators use Oracle Wallet Manager to manage public key security credentials on Oracle clients and servers. The wallets it creates can be read by Oracle Database, Oracle Application Server 10g, and the Oracle Identity Management infrastructure.
This chapter describes Oracle Wallet Manager using the following topics:
See Also:
"Public Key Infrastructure in an Oracle Environment", which discusses all of the Oracle PKI components
Appendix F, "orapki Utility" for information about the orapki command line utility you can use to create wallets and issue certificates for testing purposes
Oracle Wallet Manager is an application that wallet owners use to manage and edit the security credentials in their Oracle wallets. A wallet is a password-protected container used to store authentication and signing credentials, including private keys, certificates, and trusted certificates needed by SSL. You can use Oracle Wallet Manager to perform the following tasks:
Creating wallets
Generating certificate requests
Opening wallets to access PKI-based services
Saving credentials to hardware security modules, by using APIs that comply with the Public-Key Cryptography Standards #11 (PKCS #11) specification
Uploading wallets to (and downloading them from) an LDAP directory
Importing third-party PKCS #12-format wallets
Exporting Oracle wallets to a third-party environment
Oracle Wallet Manager provides the following features:
Oracle wallets are password protected. Oracle Wallet Manager includes an enhanced wallet password management module that enforces Password Management Policy guidelines, including the following:
Minimum password length (8 characters)
Maximum password length unlimited
Alphanumeric character mix required
Oracle Wallet Manager stores private keys associated with X.509 certificates and uses Triple-DES encryption.
Oracle Wallet Manager lets you store multiple Oracle wallets in a Windows file management system or in the user profile area of the Microsoft Windows system registry. Storing your wallets in the registry provides the following benefits:
Better Access Control: Wallets stored in the user profile area of the registry are only accessible by the associated user. User access controls for the system thus become, by extension, access controls for the wallets. In addition, when a user logs out of a system, access to that user's wallets is effectively precluded.
Easier Administration: Wallets are associated with specific user profiles, so no file permissions need to be managed, and the wallets stored in the profile are automatically deleted when the user profile is deleted. You can use Oracle Wallet Manager to create and manage the wallets in the registry.
Open a wallet from the registry
Save a wallet to the registry
Save As to a different registry location
Delete a wallet from the registry
Open a wallet from the file system and save it to the registry
Open a wallet from the registry and save it to the file system
Oracle Wallet Manager is backward-compatible to Release 8.1.7.
RSA Laboratories, a division of RSA Security, Inc., has developed, in cooperation with representatives from industry, academia, and government, a family of basic cryptography standards called Public-Key Cryptography Standards, or PKCS for short. These standards establish interoperability between computer systems that use public-key technology to secure data across intranets and the Internet.
Oracle Wallet Manager stores X.509 certificates and private keys in PKCS #12 format, and generates certificate requests according to the PKCS #10 specification. These capabilities make the Oracle wallet structure interoperable with supported third-party PKI applications and provide wallet portability across operating systems.
Oracle Wallet Manager wallets can store credentials on hardware security modules that use APIs conforming to the PKCS #11 specification. When a wallet is created with PKCS11 chosen as the wallet type, then all keys stored in that wallet are saved to a hardware security module or token. Examples of such hardware devices include smart cards, PCMCIA cards, smart diskettes, or other portable hardware devices that store private keys or perform cryptographic operations (or both).
Note:
To use Oracle Wallet Manager with PKCS #11 integration on the 64-bit Solaris Operating System, enter the following at the command line:
owm -pkcs11See Also:
"Importing User Certificates Created with a Third-Party Tool"
"Creating a Wallet to Store Hardware Security Module Credentials"
To view PKCS standards documents, navigate to the following URL:
http://www.rsasecurity.com/rsalabs/
Oracle Wallet Manager enables you to store multiple certificates in each wallet, supporting any of the following Oracle PKI certificate usages:
SSL authentication
S/MIME signature
S/MIME encryption
Code-Signing
CA Certificate Signing
Each certificate request you create generates a unique private/public key pair. The private key stays in the wallet and the public key is sent with the request to a certificate authority. When that certificate authority generates your certificate and signs it, you can import it only into the wallet that has the corresponding private key.
If the wallet also contains a separate certificate request, the private/public key pair corresponding to that request is of course different from the pair for the first certificate request. Sending this separate certificate request to a certificate authority can get you a separate signed certificate, which you can import into this same wallet
A single certificate request can be sent to a certificate authority multiple times to obtain multiple certificates. However, only one certificate corresponding to that certificate request can be installed in the wallet.
Oracle Wallet Manager uses the X.509 Version 3 KeyUsage extension to define Oracle PKI certificate usages (Table 9-1). A single certificate cannot be applied to all possible certificate usages. Table 9-2 and Table 9-3 show legal usage combinations.
Table 9-1 KeyUsage Values
| Value | Usage |
|---|---|
|
0 |
digitalSignature |
|
1 |
nonRepudiation |
|
2 |
keyEncipherment |
|
3 |
dataEncipherment |
|
4 |
keyAgreement |
|
5 |
keyCertSign |
|
6 |
cRLSign |
|
7 |
encipherOnly |
|
8 |
decipherOnly |
When installing a certificate, Oracle Wallet Manager maps the KeyUsage extension values to Oracle PKI certificate usages as specified in Table 9-2 and Table 9-3.
Table 9-2 Oracle Wallet Manager Import of User Certificates to an Oracle Wallet
| KeyUsage Value | Critical?Foot 1 | Usage |
|---|---|---|
|
none |
NA |
Certificate is importable for SSL or S/MIME encryption use. |
|
0 alone or along with any values excluding 5 and 2 |
NA |
Accept certificate for S/MIME signature or code-signing use. |
|
1 alone |
Yes |
Not importable |
|
1 alone |
No |
Accept certificate for S/MIME signature or code-signing use. |
|
2 alone or along with any combination excluding 5 |
NA |
Accept certificate for SSL or S/MIME encryption use. |
|
5 alone or along with any other values |
NA |
Accept certificate for CA certificate signing use. |
|
Any settings not listed previously |
Yes |
Not importable. |
|
Any settings not listed previously |
No |
Certificate is importable for SSL or S/MIME encryption use. |
Footnote 1 If the KeyUsage extension is critical, the certificate cannot be used for other purposes.
Table 9-3 Oracle Wallet Manager Import of Trusted Certificates to an Oracle Wallet
| KeyUsage Value | Critical?Foot 1 | Usage |
|---|---|---|
|
none |
NA |
Importable. |
|
Any combination excluding 5 |
Yes |
Not importable. |
|
Any combination excluding 5 |
No |
Importable |
|
5 alone or along with any other values |
NA |
Importable. |
Footnote 1 If the KeyUsage extension is marked critical, the certificate cannot be used for other purposes.
You should obtain, from the certificate authority, certificates with the correct KeyUsage value matching your required Oracle PKI certificate usage. A single wallet can contain multiple key pairs for the same usage. Each certificate can support multiple Oracle PKI certificate usages, as indicated by Table 9-2 and Table 9-3. Oracle PKI applications use the first certificate containing the required PKI certificate usage.
For example, for SSL usage, the first certificate containing the SSL Oracle PKI certificate usage is used.
If you do not have a certificate with SSL usage, then an ORA-28885 error (No certificate with required key usage found) is returned.
Oracle Wallet Manager can upload wallets to and retrieve them from an LDAP-compliant directory. Storing wallets in a centralized LDAP-compliant directory lets users access them from multiple locations or devices, ensuring consistent and reliable user authentication while providing centralized wallet management throughout the wallet life cycle. To prevent a user from accidentally overwriting functional wallets, only wallets containing an installed certificate can be uploaded.
Directory user entries must be defined and configured in the LDAP directory before Oracle Wallet Manager can be used to upload or download wallets for a user. If a directory contains Oracle8i (or prior) users, then they are automatically upgraded to use the wallet upload and download feature on first use.
Oracle Wallet Manager downloads a user wallet by using a simple password-based connection to the LDAP directory. However, for uploads it uses an SSL connection if the open wallet contains a certificate with SSL Oracle PKI certificate usage. If an SSL certificate is not present in the wallet, password-based authentication is used.
Note:
The directory password and the wallet password are independent and can be different. Oracle recommends that these passwords be maintained to be consistently different, where neither one can logically be derived from the other.See Also:
Multiple Certificate Support, for more information about Oracle PKI certificate usage.
To start Oracle Wallet Manager:
(Windows) Select Start, Programs, Oracle-HOME_NAME, Integrated Management Tools, Wallet Manager
(UNIX) At the command line, enter owm.
Wallets provide a necessary repository in which you can securely store your user certificates and the trust point you need to validate the certificates of your peers.
The following steps provide an overview of the complete wallet creation process:
Use Oracle Wallet Manager to create a new wallet:
Generate a certificate request. Note that when you create a new wallet with Oracle Wallet Manager, the tool automatically prompts you to create a certificate request.
Send the certificate request to the CA you want to use. You can copy and paste the certificate request text into an e-mail message, or you can export the certificate request to a file. The certificate request becomes part of your wallet. It must remain there until you remove its associated certificate.
When the CA sends your signed user certificate and its associated trusted certificate, then you can import these certificates in the following order. The user certificates and trusted certificates in the PKCS #7 format can be imported at the same time.
First import the CA's trusted certificate into your wallet. This step may be optional if the new user certificate has been issued by one of the CAs whose trusted certificate is already present in Oracle Wallet Manager by default.
After you have successfully imported the trusted certificate, then import the user certificate that the CA sent to you into your wallet.
(Optional) Set the auto login feature for your wallet.
Typically, this feature, which enables PKI-based access to services without a password, is required for most wallets. It is required for database server and client wallets. It is only optional for products that take the wallet password at the time of startup.
After completing the preceding process, you have a wallet that contains a user certificate and its associated trust points.
See Also:
For more information about these steps, refer to Managing CertificatesThis section describes how to create a new wallet and perform associated wallet management tasks, such as generating certificate requests, exporting certificate requests, and importing certificates into wallets, in the following subsections:
Because an Oracle wallet contains user credentials that can be used to authenticate the user to multiple databases, it is especially important to choose a strong wallet password. A malicious user who guesses the wallet password can access all the databases to which the wallet owner has access.
Passwords must contain at least eight characters that consist of alphabetic characters combined with numbers or special characters.
Caution:
It is strongly recommended that users avoid choosing easily guessed passwords based on user names, phone numbers, or government identification numbers, such as "admin0," "oracle1," or "2135551212A." This prevents a potential attacker from using personal information to deduce the users' passwords. It is also a prudent security practice for users to change their passwords periodically, such as once in each month or once in each quarter.When you change passwords, you must regenerate auto-login wallets.
See Also:
You can use Oracle Wallet Manager to create PKCS #12 wallets (the standard default wallet type) that store credentials in a directory on your file system. It can also be used to create PKCS #11 wallets that store credentials on a hardware security module for servers, or private keys on tokens for clients. The following sections explain how to create both types of wallets by using Oracle Wallet Manager.
Unless you have a hardware security module (a PKCS #11 device), then you should use a standard wallet that stores credentials in a directory on your file system.
To create a standard wallet, perform the following tasks:
Select Wallet, then New from the menu bar. The New Wallet dialog box is displayed.
Follow the "Required Guidelines for Creating Wallet Passwords" and enter a password in the Wallet Password field. This password protects unauthorized use of your credentials.
Reenter that password in the Confirm Password field.
Select Standard from the Wallet Type list.
Click OK to continue. If the entered password does not conform to the required guidelines, then the following message is displayed:
Password must have a minimum length of eight characters, and contain alphabetic characters combined with numbers or special characters. Do you want to try again?
An alert is displayed, and informs you that a new empty wallet has been created. It prompts you to decide whether you want to add a certificate request. Refer to "Adding a Certificate Request".
If you select No, then you are returned to the Oracle Wallet Manager main window. The new wallet you just created is displayed in the left window pane. The certificate has a status of [Empty], and the wallet displays its default trusted certificates.
Select Wallet, then Save In System Default to save the new wallet.
If you do not have permission to save the wallet in the system default, you can save it to another location. This location must be used in the SSL configuration for clients and servers.
A message at the bottom of the window confirms that the wallet was successfully saved.
To create a wallet to store credentials on a hardware security module that complies with PKCS #11, perform the following tasks:
Select Wallet, then New from the menu bar. The New Wallet dialog box is displayed.
Follow the "Required Guidelines for Creating Wallet Passwords" and enter a password in the Wallet Password field.
Reenter that password in the Confirm Password field.
Select PKCS11 from the Wallet Type list, and click OK to continue. The New PKCS11 Wallet window is displayed.
Select a vendor name from the Select Hardware Vendor list.
Note:
In the current release of Oracle Wallet Manager, SafeNET and nCipher hardware have been certified to interoperate with Oracle wallets.In the PKCS11 library filename field, enter the path to the directory where the PKCS11 library is stored, or click Browse to find it by searching the file system.
Enter the SmartCard password, and click OK.
The smart card password, which is different from the wallet password, is stored in the wallet.
An alert is displayed, and informs you that a new empty wallet has been created. It prompts you to decide whether you want to add a certificate request. For more information, refer to "Adding a Certificate Request".
If you select No, you are returned to the Oracle Wallet Manager main window. The new wallet you just created is displayed in the left window pane. The certificate has a status of [Empty], and the wallet displays its default trusted certificates.
Select Wallet, then Save In System Default to save the new wallet.
If you do not have permission to save the wallet in the system default, you can save it to another location.
A message at the bottom of the window confirms that the wallet was successfully saved.
Note:
If you change the smart card password or move the PKCS #11 library, an error message displays when you try to open the wallet. Then you are prompted to enter the new smart card password or the new path to the library.Open a wallet that already exists in the file system directory as follows:
Select Wallet, Open from the menu bar. The Select Directory dialog box is displayed.
Navigate to the directory location in which the wallet is located, and select the directory.
Click OK. The Open Wallet dialog box is displayed.
Enter the wallet password in the Wallet Password field.
Click OK.
You are returned to the main window and a message is displayed at the bottom of the window indicating the wallet was opened successfully. The wallet's certificate and its trusted certificates are displayed in the left window pane.
To close an open wallet in the currently selected directory:
Select Wallet, then Close.
A message is displayed at the bottom of the window to confirm that the wallet is closed.
Oracle Wallet Manager can export its own wallets to third-party environments.
To export a wallet to third-party environments:
Use Oracle Wallet Manager to save the wallet file.
Follow the procedure specific to your third-party product to import an operating system PKCS #12 wallet file created by Oracle Wallet Manager (called ewallet.p12 on UNIX and Windows platforms).
Note:
Oracle Wallet Manager supports multiple certificates for each wallet, yet current browsers typically support import of single-certificate wallets only. For these browsers, you must export an Oracle wallet containing a single key-pair.
Oracle Wallet Manager supports wallet export to only Netscape Communicator 4.7.2 and later, OpenSSL, and Microsoft Internet Explorer 5.0 and later.
You can export a wallet to a text-based PKI format if you want to put a wallet into a tool that does not support PKCS #12. Individual components are formatted according to the standards listed in Table 9-4. Within the wallet, only those certificates with SSL key usage are exported with the wallet.
To export a wallet to text-based PKI format:
Select Operations, Export Wallet. The Export Wallet dialog box is displayed.
Enter the destination file system directory for the wallet, or navigate to the directory structure under Folders.
Enter the destination file name for the wallet.
Click OK to return to the main window.
To upload a wallet to an LDAP directory, Oracle Wallet Manager uses SSL if the specified wallet contains an SSL certificate. Otherwise, it lets you enter the directory password.
To prevent accidental destruction of your wallet, Oracle Wallet Manager will not permit you to execute the upload option unless the target wallet is currently open and contains at least one user certificate.
To upload a wallet:
Select Wallet, Upload Into The Directory Service. If the currently open wallet has not been saved, a dialog box is displayed with the following message:
The wallet needs to be saved before uploading
Click Yes to proceed.
Wallet certificates are checked for SSL key usage. Depending on whether a certificate with SSL key usage is found in the wallet, one of the following results occur:
If at least one certificate has SSL key usage: When prompted, enter the LDAP directory server host name and port information, then click OK. Oracle Wallet Manager attempts connection to the LDAP directory server using SSL. A message is displayed indicating whether the wallet was uploaded successfully or it failed.
If no certificates have SSL key usage: When prompted, enter the user's distinguished name (DN), the LDAP server host name and port information, and click OK. Oracle Wallet Manager attempts connection to the LDAP directory server using simple password authentication mode, assuming that the wallet password is the same as the directory password.
If the connection fails, a dialog box prompts for the directory password of the specified DN. Oracle Wallet Manager attempts connection to the LDAP directory server using this password and displays a warning message if the attempt fails. Otherwise, Oracle Wallet Manager displays a status message at the bottom of the window indicating that the upload was successful.
Note:
You should ensure that the distinguished name used matches a corresponding user entry of object class inetOrgPerson in the LDAP directory.
When uploading a wallet with an SSL certificate, use the SSL port. When uploading a wallet that does not contain an SSL certificate, use the non-SSL port.
When a wallet is downloaded from an LDAP directory, it is resident in working memory. It is not saved to the file system unless you explicitly save it using any of the save options described in the following sections.
To download a wallet from an LDAP directory:
Select Wallet, Download From The Directory Service....
A dialog box prompts for the user's distinguished name (DN), and the LDAP directory password, host name, and port information. Oracle Wallet Manager uses simple password authentication to connect to the LDAP directory.
Depending on whether the downloading operation succeeds or not, one of the following results occurs:
If the download operation fails: Check to make sure that you have correctly entered the user's DN, and the LDAP server host name and port information. The port used must be the non-SSL port.
If the download is successful: Click OK to open the downloaded wallet. Oracle Wallet Manager attempts to open that wallet using the directory password. If the operation fails after using the directory password, then a dialog box prompts for the wallet password.
If Oracle Wallet Manager cannot open the target wallet using the wallet password, then check to make sure you entered the correct password. Otherwise a message displays at the bottom of the window, indicating that the wallet was downloaded successfully.
To save your changes to the current open wallet:
Select Wallet, then Save.
A message at the bottom of the window confirms that the wallet changes were successfully saved to the wallet in the selected directory location.
To save open wallets to a new location, use the Save As menu option:
Select Wallet, then Save As. The Select Directory dialog box is displayed.
Select a directory location in which to save the wallet.
Click OK.
The following message is displayed if a wallet already exists in the selected location:
A wallet already exists in the selected path. Do you want to overwrite it?
Select Yes to overwrite the existing wallet or No to save the wallet to another location.
A message at the bottom of the window confirms that the wallet was successfully saved to the selected directory location.
To save wallets in the default directory location, use the Save In System Default menu option:
Select Wallet, Save In System Default.
A message at the bottom of the window confirms that the wallet was successfully saved in the system default wallet location as follows for UNIX and Windows platforms:
(UNIX) etc/ORACLE/WALLETS/username
(Windows) %USERPROFILE%\ORACLE\WALLETS
Note:
SSL uses the wallet that is saved in the system default directory location.
Some Oracle applications are not able to use the wallet if it is not in the system default location. Check the Oracle documentation for your specific application to determine whether wallets must be placed in the default wallet directory location.
To delete the current open wallet:
Select Wallet, Delete. The Delete Wallet dialog box is displayed.
Review the displayed wallet location to verify you are deleting the correct wallet.
Enter the wallet password.
Click OK. A dialog panel is displayed to inform you that the wallet was successfully deleted.
Note:
Any open wallet in application memory will remain in memory until the application exits. Therefore, deleting a wallet that is currently in use does not immediately affect system operation.A password change is effective immediately. The wallet is saved to the currently selected directory, encrypted with the password.
Note:
If you are using a wallet with auto login enabled, you must regenerate the auto login wallet after changing the password. Refer to "Using Auto Login"To change the password for the current open wallet:
Select Wallet, then Change Password. The Change Wallet Password dialog box is displayed.
Enter the existing wallet password.
Enter the new password.
Reenter the new password.
Click OK.
A message at the bottom of the window confirms that the password was successfully changed.
See Also:
"Wallet Password Management", for password policy restrictions
PKI-based access to services can be enabled without requiring human interventions to supply the necessary passwords: this feature is called auto login. Enabling auto login creates an obfuscated copy of the wallet, which is then used automatically until the auto login feature is disabled for that wallet.
Auto login wallets are protected by file system permissions. When auto login is enabled for a wallet, only the operating system user who created it can manage it, through the Oracle Wallet Manager.
You must enable auto login if you want single sign-on access to multiple Oracle databases: such access is normally disabled, by default. Sometimes the obfuscated auto login wallets are called "SSO wallets" because they support single sign-on capability.
To enable auto login:
Select Wallet from the menu bar.
Select Auto Login. A message at the bottom of the window indicates that auto login is enabled.
To disable auto login:
Select Wallet from the menu bar.
Deselct Auto Login. A message at the bottom of the window indicates that auto login is disabled.
All certificates are signed data structures that bind a network identity with a corresponding public key. Table 9-5 describes the two types of certificates distinguished in this chapter.
Table 9-5 Types of Certificates
| Certificate Type | Examples |
|---|---|
|
User certificates |
Certificates issued to servers or users to prove an end entity's identity in a public key/private key exchange |
|
Trusted certificates |
Certificates representing entities whom you trust, such as certificate authorities who sign the user certificates they issue |
The following subsections describe how to manage both types of certificates:
Note:
Before a user certificate can be installed, the wallet must contain the trusted certificate representing the certificate authority who issued that user certificate. However, whenever you create a new wallet, several publicly trusted certificates are automatically installed, since they are so widely used. If the necessary certificate authority is not represented, then you must install its certificate first.Also, you can import using the PKCS#7 certificate chain format, which gives you the user certificate and the CA certificate at the same time.
User certificates, including server certificates, are used by end users, smart cards, or applications, such as Web servers. For example, if a CA issues a certificate for a Web server, placing its distinguished name (DN) in the Subject field, then the Web server is the certificate owner, thus the "user" for this user certificate.
Managing user certificates involves the following tasks:
You can add multiple certificate requests with Oracle Wallet Manager. When adding multiple requests, Oracle Wallet Manager automatically populates each subsequent request dialog box with the content of the initial request that you can then edit.
The actual certificate request becomes part of the wallet. You can reuse any certificate request to obtain a new certificate. However, you cannot edit an existing certificate request. Store only a correctly filled out certificate request in a wallet.
To create a PKCS #10 certificate request:
Select Operations, then Add Certificate Request. The Add Certificate Request dialog box is displayed.
Note:
The online Help for Oracle Wallet Manager becomes unresponsive when modal dialog boxes appear, such as the one for entering certificate request information. The online Help becomes responsive once the modal dialog box is closed.Enter the information specified in Table 9-6.
Click OK. A message informs you that a certificate request was successfully created. You can either copy the certificate request text from the body of this dialog panel and paste it into an e-mail message to send to a certificate authority, or you can export the certificate request to a file. At this point, Oracle Wallet Manager has created your private/public key pair and stored it in the wallet. When the certificate authority issues your certificate, it will also be stored in the wallet and associate it with its corresponding private key.
Click OK to return to the Oracle Wallet Manager main window. The status of the certificate changes to [Requested].
See Also:
"Exporting a User Certificate Request"Table 9-6 Certificate Request: Fields and Descriptions
| Field Name | Description |
|---|---|
|
Common Name |
Mandatory. Enter the name of the user's or service's identity. Enter a user's name in first name /last name format. Example: Eileen.Sanger |
|
Organizational Unit |
Optional. Enter the name of the identity's organizational unit. Example: Finance. |
|
Organization |
Optional. Enter the name of the identity's organization. Example: XYZ Corp. |
|
Locality/City |
Optional. Enter the name of the locality or city in which the identity resides. |
|
State/Province |
Optional. Enter the full name of the state or province in which the identity resides. Enter the full state name, because some certificate authorities do not accept two–letter abbreviations. |
|
Country |
Mandatory. Select Country to view a list of country abbreviations. Select the country in which the organization is located. |
|
Key Size |
Mandatory. Select Key Size to view a list of key sizes to use when creating the public/private key pair. Refer to Table 9-7 to evaluate key size. |
|
Advanced |
Optional. Select Advanced to view the Advanced Certificate Request dialog panel. Use this field to edit or customize the identity's distinguished name (DN). For example, you can edit the full state name and locality. |
Table 9-7 lists the available key sizes and the relative security each size provides. Typically, CAs use key sizes of 1024 or 2048. When certificate owners wish to keep their keys for a longer duration, they choose 3072 or 4096 bit keys.
When the Certificate Authority grants you a certificate, it may send you an e-mail that has your certificate in text (BASE64) form or attached as a binary file.
Note:
Certificate authorities may send your certificate in a PKCS #7 certificate chain or as an individual X.509 certificate. Oracle Wallet Manager can import both types.PKCS #7 certificate chains are a collection of certificates, including the user's certificate and all of the supporting trusted CA and subCA certificates.
In contrast, an X.509 certificate file contains an individual certificate without the supporting certificate chain.
However, before you can import any such individual certificate, the signer's certificate must be a Trusted Certificate in the wallet.
Copy the certificate, represented as text (BASE64), from the e-mail message. Include the lines Begin Certificate and End Certificate.
Select Operations, Import User Certificate. The Import Certificate dialog box is displayed.
Select Paste the certificate, and then click OK. Another Import Certificate dialog box is displayed with the following message:
Please provide a base64 format certificate and paste it below.
Paste the certificate into the dialog box, and click OK.
If the certificate received is in PKCS#7 format, it is installed, and all the other certificates included with the PKCS#7 data are placed in the Trusted Certificate list.
If the certificate received is not in PKCS#7 format, and the certificate of its CA is not already in the Trusted Certificates list, then more must be done. Oracle Wallet Manager will ask you to import the certificate of the CA that issued your certificate. This CA certificate will be placed in the Trusted Certificates list. (If the CA certificate was already in the Trusted Certificates list, your certificate is imported without additional steps.)
After either (a) or (b) succeeds, a message at the bottom of the window confirms that the certificate was successfully installed. You are returned to the Oracle Wallet Manager main panel, and the status of the corresponding entry in the left panel subtree changes to [Ready].
Note:
The standard X.509 certificate includes the following start and end text:-----BEGIN CERTIFICATE----- -----END CERTIFICATE-----
A typical PKCS#7 certificate includes more, as described earlier, and includes the following start and end text:
-----BEGIN PKCS7----- -----END PKCS7-----
You can use the standard Ctrl+c to copy, including all dashes, and Ctrl+v to paste.
The user certificate in the file can be in either text (BASE64) or binary (der) format.
Select Operations, Import User Certificate. The Import Certificate dialog box is displayed.
Select Select a file that contains the certificate, and click OK. Another Import Certificate dialog box is displayed.
Enter the path or folder name of the certificate file location.
Select the name of the certificate file (for example, cert.txt, cert.der).
Click OK.
If the certificate received is in PKCS#7 format, it is installed, and all the other certificates included with the PKCS#7 data are placed in the Trusted Certificate list.
If the certificate received is not in PKCS#7 format, and the certificate of its CA is not already in the Trusted Certificates list, then more must be done. Oracle Wallet Manager will ask you to import the certificate of the CA that issued your certificate. This CA certificate will be placed in the Trusted Certificates list. (If the CA certificate was already in the Trusted Certificates list, your certificate is imported without additional steps.)
After either (a) or (b) succeeds, a message at the bottom of the window confirms that the certificate was successfully installed. You are returned to the Oracle Wallet Manager main panel, and the status of the corresponding entry in the left panel subtree changes to [Ready].
Third-party certificates are those created from certificate requests that were not generated using Oracle Wallet Manager. These third-party certificates are actually wallets, in the Oracle sense, because they contain more than just the user certificate; they also contain the private key for that certificate. Furthermore, they include the chain of trusted certificates validating that the certificate was created by a trustworthy entity.
Oracle Wallet Manager makes these wallets available in a single step by importing them in PKCS#12 format, which includes all three elements described earlier: the user certificate, the private key, and the trusted certificates. It supports the following PKCS #12-format certificates:
Oracle Wallet Manager adheres to the PKCS#12 standard, so certificates exported by any PKCS#12-compliant tool should be usable with Oracle Wallet Manager.
Such third-party certificates cannot be stored into existing Oracle wallets because they would lack the private key and chain of trusted authorities. Therefore, each such certificate is exported and retrieved instead as an independent PKCS#12 file, that is, as its own wallet.
Once a third party generates the wallet, you need to import it to make use of it, as described in this section.
To import a certificate created with a third-party tool, perform the following tasks:
Follow the procedures for your particular product to export the certificate. Take the actions indicated in the exporting product to include the private key in the export, and specify the new password to protect the exported certificate. Also include all associated trust points. (Under PKCS #12, browsers do not necessarily export trusted certificates, other than the signer's own certificate. You may need to add additional certificates to authenticate to your peers. You can use Oracle Wallet Manager to import trusted certificates.)
The resulting file, containing the certificate, the private key, and the trust points, is the new wallet that enables the third-party certificate to be used.
To be used by particular applications or servers, such as a web server or an LDAP server, wallets need to be located precisely. Each application has its own expectations as to which directory it will search to find the needed wallet. You must put the wallet where it will be sought, by copying it to the correct system and directory.
For use with UNIX or Windows applications or servers, the wallet must be named ewallet.p12.
For other operating systems, refer to the Oracle documentation for that specific operating system.
Once a third-party certificate is stored as ewallet.p12, you can open and manage it using Oracle Wallet Manager. You will have to supply the password you created when exporting this wallet.
Note:
The password will be required whenever the associated application starts up or otherwise needs the certificate. To make such access automatic, refer to "Using Auto Login".However, if the private key for the desired certificate is held in a separate hardware security module,you will not be able to import that certificate.
To remove a user certificate from a wallet:
In the left panel subtree, select the certificate that you want to remove.
Select Operations, then Remove User Certificate. A dialog panel is displayed which prompts you to verify that you want to remove the user certificate from the wallet.
Select Yes to return to the Oracle Wallet Manager main panel. The certificate displays a status of [Requested].
You must remove a certificate before removing its associated request.
To remove a certificate request:
In the left panel subtree, select the certificate request that you want to remove.
Select Operations, then Remove Certificate Request.
Click Yes. The certificate displays a status of [Empty].
To save the certificate in a file system directory, export the certificate by using the following steps:
In the left panel subtree, select the certificate that you want to export.
Select Operations, then Export User Certificate from the menu bar. The Export Certificate dialog box is displayed.
Enter the file system directory location where you want to save your certificate, or navigate to the directory structure under Folders.
Enter a file name for your certificate in the Enter File Name field.
Click OK. A message at the bottom of the window confirms that the certificate was successfully exported to the file. You are returned to the Oracle Wallet Manager main window.
See Also:
"Exporting Oracle Wallets to Third-Party Environments" for information about exporting wallets. Note that Oracle Wallet Manager supports storing multiple certificates in a single wallet, yet current browsers typically support only single-certificate wallets. For these browsers, you must export an Oracle wallet that contains a single key-pair.To save the certificate request in a file system directory, export the certificate request by using the following steps:
In the left panel subtree, select the certificate request that you want to export.
Select Operations, then Export Certificate Request. The Export Certificate Request dialog box is displayed.
Enter the file system directory location where you want to save your certificate request, or navigate to the directory structure under Folders.
Enter a file name for your certificate request, in the Enter File Name field.
Select OK. A message at the bottom of the window confirms that the certificate request was successfully exported to the file. You are returned to the Oracle Wallet Manager main window.
Managing trusted certificates includes the following tasks:
You can import a trusted certificate into a wallet in either of two ways: paste the trusted certificate from an e-mail that you receive from the certificate authority, or import the trusted certificate from a file.
Oracle Wallet Manager automatically installs trusted certificates from VeriSign, RSA, Entrust, and GTE CyberTrust when you create a new wallet.
Copy the trusted certificate from the body of the e-mail message you received that contained the user certificate. Include the lines Begin Certificate and End Certificate.
Select Operations, then Import Trusted Certificate from the menu bar. The Import Trusted Certificate dialog panel is displayed.
Select Paste the Certificate and click OK. Another Import Trusted Certificate dialog panel is displayed with the following message:
Please provide a base64 format certificate and paste it below.
Paste the certificate into the window, and click OK. A message at the bottom of the window informs you that the trusted certificate was successfully installed.
Click OK. You are returned to the Oracle Wallet Manager main panel, and the trusted certificate is displayed at the bottom of the Trusted Certificates tree.
Keyboard shortcuts for copying and pasting certificates:
Use Ctrl+c to copy, and use Ctrl+v to paste.
The file containing the trusted certificate should have been saved in either text (BASE64) or binary (der) format.
Select Operations, then Import Trusted Certificate. The Import Trusted Certificate dialog panel is displayed.
Enter the path or folder name of the trusted certificate location.
Select the name of the trusted certificate file (for example, cert.txt).
Click OK. A message at the bottom of the window informs you that the trusted certificate was successfully imported into the wallet.
Click OK to exit the dialog panel. You are returned to the Oracle Wallet Manager main panel, and the trusted certificate is displayed at the bottom of the Trusted Certificates tree.
You cannot remove a trusted certificate if it has been used to sign a user certificate still present in the wallet. To remove such trusted certificates, you must first remove the certificates it has signed. Also, you cannot verify a certificate after its trusted certificate has been removed from your wallet.
To remove a trusted certificate from a wallet:
Select the trusted certificate listed in the Trusted Certificates tree.
Select Operations, then Remove Trusted Certificate... from the menu bar.
A dialog panel warns you that your user certificate will no longer be verifiable by its recipients if you remove the trusted certificate that was used to sign it.
Select Yes. The selected trusted certificate is removed from the Trusted Certificates tree.
To export a trusted certificate to another file system location:
In the left panel subtree, select the trusted certificate that you want to export.
Select Operations, thenExport Trusted Certificate. The Export Trusted Certificate dialog box is displayed.
Enter a file system directory in which you want to save your trusted certificate, or navigate to the directory structure under Folders.
Enter a file name to save your trusted certificate.
Click OK. You are returned to the Oracle Wallet Manager main window.
To export all of your trusted certificates to another file system location:
Select Operations, then Export All Trusted Certificates.... The Export Trusted Certificate dialog box is displayed.
Enter a file system directory location where you want to save your trusted certificates, or navigate to the directory structure under Folders.
Enter a file name to save your trusted certificates.
Click OK. You are returned to the Oracle Wallet Manager main window.
|
 Copyright © 1996, 2009, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|