Files and Artifacts Generated by RREG
The files that get generated by the RREG Tool vary, depending on the security level you are using for communications between the WebGate and the Oracle Access Manager server. See Securing Communication Between OAM Servers and WebGates in Administrator's Guide for Oracle Access Management.
Note that in this topic any references to RREG_HOME
should be replaced with the path to the directory where you ran the RREG tool. This is typically the following directory on the Oracle Access Manager server, or (if you are using out-of-band mode) the directory where you unpacked the RREG archive:
OAM_ORACLE_HOME/oam/server/rreg/client
The following table lists the artifacts that are always generated by the RREG Tool, regardless of the Oracle Access Manager security level.
File | Location |
---|---|
cwallet.sso |
|
ObAccessClient.xml |
RREG_HOME/output/Agent_ID/ |
The following table lists the additional files that are created if you are using the SIMPLE or CERT security level for Oracle Access Manager:
File | Location |
---|---|
aaa_key.pem |
RREG_HOME/output/Agent_ID/ |
aaa_cert.pem |
RREG_HOME/output/Agent_ID/ |
password.xml |
RREG_HOME/output/Agent_ID/ |
Note that the password.xml
file contains the obfuscated global passphrase to encrypt the private key used in SSL. This passphrase can be different than the passphrase used on the server.
You can use the files generated by RREG to generate a certificate request and get it signed by a third-party Certification Authority. To install an existing certificate, you must use the existing aaa_cert.pem
and aaa_chain.pem
files along with password.xml
and aaa_key.pem
.