Chapter 5: Security
SQL Option security measures control access to the system and protect data stored in table objects. If the security option is turned on at both the server and on the client, you will be prompted for a user ID and password when you compile using the VALIDATE preprocessor directive or execute a program containing embedded SQL. For more information on setting up security and authority, see the following:
Using the Logon and Logoff Commands
Use the SQL Option Logon and Logoff commands to avoid repeatedly logging into an XDB Server or SQL Option Link during the compile and test phase of development.
To log on to the SQL Option Server once per session, follow these steps:
From the Tools menu, select SQL Option
Select Logon
Enter your user ID and password
The SQL Option Server will automatically reuse your user ID and password each time you compile or execute the program, until you select Logoff or restart your system.
Validating Tables
The following describes how to set up your environment to validate tables during the compile process:
- With Security Off, the user ID will be the same authorization ID defined as the primary ID unless you define a secondary ID.
- With Security On, the user ID will be the same ID that you enter in the logon screen and optionally the secondary ID if defined (not applicable to SQL Option Link).
To access tables with the same user ID and authorization ID, use the VALIDATE preprocessor directive. To access tables with different user ID and authorization ID, do one of the following:
- Use VALIDATE and AUTHID preprocessor directives.
- Define group IDs or issue a GRANT to the user ID to have access to the authorization ID defined in the AUTHID preprocessor directive.
- Define secondary IDs.
Copyright © 2007 Micro Focus (IP) Ltd. All rights reserved.