Table of Contents

Search

  1. Preface
  2. Installation Overview
  3. Installing MDM Registry Edition
  4. Post-Installation Tasks
  5. Troubleshooting
  6. Upgrading MDM Registry Edition
  7. Uninstalling MDM Registry Edition

Installation and Configuration Guide

Installation and Configuration Guide

Configuring MDM Registry Edition Security Server

Configuring MDM Registry Edition Security Server

Configure the Security Server that exposes the security framework authentication APIs over SSL to authenticate the Informatica Data Director client. MDM Registry Edition uses a secure channel to communicate with the Security Server to run the security framework.
By default, the Security Server uses LDAP security provider. To use the database security provider, update the
<MDM Registry Edition Installation Directory>\bin\secup
file on Windows or
<MDM Registry Edition Installation Directory>/bin/secup
file on UNIX with the
-tDB
option as follows:
start /b %SSAJAVA% -Djavax.net.ssl.keyStore=%SSA_SEC_KEYSTORE% ^ -Djavax.net.ssl.keyStorePassword=%SSA_SEC_KEYPASSWORD% ^ -Djava.util.logging.config.file="d:\\logging.properties" ^ -classpath "%SSA_SEC_CLASSPATH%" com.informatica.rbss.server.impl.SecurityServer ^ -w%SSASERVERWORKDIR% -h%SSA_SSHOST% %SSA_SEC_ARGS% -tDB
Before you start MDM Registry Edition, verify the following environment variables for the Security Server and update them if required:
SSANOSECAUTHORIZATION
Indicates whether you want to disable the authorization process. If you use a database or LDAP as the security provider, you must disable the authorization process. If you disable the authorization process, the security framework does not verify whether a user has sufficient privileges to access the requested resource.
To disable the authorization process, set the
SSANOSECAUTHORIZATION
environment variable to Yes. By default, the authorization process is enabled.
SSASERVERLOGSDIR
Directory that stores the server logs. The installer sets this environment variable, and it creates the
sserver.trc
debug file in this directory.
SSA_SEC_LOGGING_PROPERTIES
Configure this environment variable only if you require custom logging. The following text shows a sample custom
logging.properties
file:
handlers = java.util.logging.ConsoleHandler, java.util.logging.FileHandler # Set the default logging level for the root logger .level = OFF # Set the default logging level for new ConsoleHandler instances java.util.logging.ConsoleHandler.level = OFF # Set the default logging level for new FileHandler instances java.util.logging.FileHandler.level = INFO # Set the default formatter for new ConsoleHandler instances java.util.logging.ConsoleHandler.formatter = java.util.logging.SimpleFormatter # Set the default logging level for the logger # use level FINE to enable debug level messages com.informatica.rbs.level = INFO com.informatica.rbss.level = INFO
SSA_SEC_LIB
Directory that contains dependent libraries for the Security Server. The default directory is as follows:
  • On Windows:
    <MDM Registry Edition Installation Directory>\security\lib
  • On UNIX:
    <MDM Registry Edition Installation Directory>/security/lib
SSA_SEC_KEYSTORE
The
server.keystore
file that contains the key for the server to run as a SSL server. The default value for this variable is as follows:
  • On Windows:
    <MDM Registry Edition Installation Directory>\security\cert\server.keystore
  • On UNIX:
    <MDM Registry Edition Installation Directory>/security/cert/server.keystore
SSA_SEC_CONFIG
Framework configuration file for the Security Server. The default value for this variable is as follows:
  • On Windows:
    <MDM Registry Edition Installation Directory>\security\SecConfig.xml
  • On UNIX:
    <MDM Registry Edition Installation Directory>/security/SecConfig.xml
SSA_SEC_DICT
Framework
.dict
file for the Security Server. If you set this variable, MDM Registry Edition does not consider the SSA_SEC_CONFIG variable.

0 COMMENTS

We’d like to hear from you!