JADE Development Environment Security

The security hooks provided by the JADE development environment enable you to install mechanisms to restrict access to tasks in the JADE development environment.

JADE development environment authentication performs the following actions.

1. Calls a user authentication routine, which validates the user identifier and password for access to the JADE development environment.

2. Calls a user hook each time a specific development task is attempted, to verify that the function is available to the user.

When a user signs on to the JADE development environment, the following actions are performed.

• JADE looks in the DevelopmentSecurityLibrary parameter in the [JadeSecurity] section of the JADE initialization file for the name of your user-defined security library (DLL). For details, see "JADE Security Section [JadeSecurity]", in the JADE Initialization File Reference.

• The compiler attempts to load the security library by calling LoadLibrary and gets the address of your predefined jadeDevelopmentUserInfo routine by calling GetProcAddress. An error is raised if the library cannot be located in the JADE executable (binary) directory or in the current path.

• When a user accesses a task (for example, a menu command), the action is passed to your user-supplied jadeDevelopmentFunctionSelected routine. An error is raised if the user does not have access to that task.

When you specify your user-defined library containing your entry points in the DevelopmentSecurityLibrary parameter in the [JadeSecurity] section of the JADE initialization file but JADE cannot find the library or its entry points, JADE development environment access security is enabled. Any developer who does not have this library or who does not have access to this library is then prevented from using the JADE development environment.

For details about the patch control security hook, see "Patch Control Hook", later in this section.