Table of Contents

Search

  1. Preface
  2. Introduction
  3. Servers
  4. Console Client
  5. Search Clients
  6. Table Loader
  7. Update Synchronizer
  8. Globalization
  9. Siebel Connector
  10. Web Services
  11. ASM Workbench
  12. Cluster Merge Rules
  13. Forced Link and Unlink
  14. System Backup and Restore
  15. Batch Utilities

ids: Interface - Encrypted Dictionary Alias

ids: Interface - Encrypted Dictionary Alias

MDM Registry Edition
can use an encrypted dictionary file to hide the actual connection string from the users who have access to the file system. The encrypted dictionary file is a text file that you can transfer through FTP in ASCII mode if needed.
On UNIX platforms, only an
MDM Registry Edition
administrator must have the read and write permissions on the file.
Use the
iirdict
utility to create an encrypted dictionary file. The utility uses the 256-bit Advanced Encryption Standard (AES) algorithm for encryption.
You can specify the name of a file that you create or update as a command line argument. If you do not specify the name as a command line argument, the utility uses the file specified in the SSA_DBDICT environment variable. If you do not set the SSA_DBDICT environment variable, the utility uses the
$SSABIN/dbdict.dic
file.
$SSABIN/iirdict xxx.dic iirdict <revision> Enter a password: Re-enter password: Operating on ’xxx.dic’ Command (a=Add d=Delete l=List t=Test q=Quit)?
If the encrypted dictionary file does not exist, the utility creates the file and prompts you to provide a password. The password does not echo at the command prompt. If the encrypted dictionary file exists, you must enter the correct password.
You can use the following commands:
  • a. Adds an entry to the encrypted dictionary.
  • d. Deletes an entry from the encrypted dictionary.
  • l. Lists the log of changes made to the encrypted dictionary.
  • t. Tests a database connection to see if it is working.
  • q. Exits the
    iirdict
    utility.
The following sample session adds an alias:
iirdict <revision> Enter password: Operating on ’xxx.dic’ Command (a=Add d=Delete l=List t=Test q=Quit)? a Enter alias: rb Enter connection details: Type (odb): System Qualifier: 1 Userid (ssa): Password: Re-enter password: Service: dbserver Connection string is ’odb:1:ssa/@dbserver’ (p=Proceed r=Re-enter d=Discard): p iirdict> alias ’rb’ tested successfully iirdict> alias ’rb’ added successfully
If you update the dictionary file, ensure that you restart the
MDM Registry Edition
servers to reflect the changes.
You can also use the HTTP authentication mechanism to encrypt the connection string. To use the HTTP authentication mechanism, specify
http
in the
Type
prompt. The following sample session uses the HTTP authentication mechanism:
iirdict <revision> Operating on 'D:\builds\a3pi\bin\dbdict.dic' Enter password: Command (a=Add d=Delete l=List t=Test q=Quit)? a Enter alias: realm Enter connection details: Type (odb): http Realm userid: user2 Realm password: iirdict> alias 'realm' added successfully Command (a=Add d=Delete l=List t=Test q=Quit)? d Comment: q
For information about these fields, see the Database Object Names section.
Password does not echo at the command prompt.
When you enter an alias, the
iirdict
utility tries to validate the connection. The alias is added regardless of any connection errors, which can be caused by an external problem, such as an incorrect ODBC or database configuration.
For example, if you want to change the connection to change the password, you must delete the connection and add it again. The
iirdict
utility does not allow the file to contain two aliases with the same name.
Use the list command to list the log of changes made to the encrypted dictionary.
Command (a=Add d=Delete l=List t=Test q=Quit)? l # Tue Feb 9 23:22:07 2010 ssa Created # Wed Feb 10 00:09:29 2010 ssa Added alias ’rb’
In this example, ssa is the name of the
MDM Registry Edition
administrator.
You can define the SSA_DBDICT environment variable in the server’s environment, as in the previous section. It defaults to
$SSABIN/dbdict.dic
.

0 COMMENTS

We’d like to hear from you!