Logon validation is a mechanism that checks user identification and password at connection time using reference data stored in the OpenEdge RDBMS.
In the OpenEdge RDBMS, the reference table storing user identifications and passwords serves both OpenEdge SQL and Progress 4GL interfaces. Use the CREATE USER statement to enable logon validation from the SQL interface. Use the OpenEdge Data Administration tool to enable logon validation from the Progress 4GL interface. Logon validation can be disabled from either interface.
Creating, altering, or dropping a user via SQL is equivalent to creating, maintaining, or deleting a user with the OpenEdge Data Administration tool. The user list updated for the OpenEdge SQL interface is updated for the Progress 4GL interface and vice-versa.
In an environment where an OpenEdge RDBMS is accessed by applications using both Progress 4GL and SQL, the following conditions exist:
If no users have been created —The Progress 4GL interface will not display a logon dialog box, but the OpenEdge SQL interface will. Anything may be entered in the user identification field and the password field may be left blank.
If users have been created —Users accessing the database through the Progress 4GL interface are required to provide an identification and password only when the DBA has specifically mandated the practice. Furthermore, users working from the 4GL interface by default have unlimited privileges. The DBA who controls access from the 4GL interface must place limitations on user privileges or restrict access to certain database objects.
Users accessing the database through the OpenEdge SQL interface are required to provide an identification and password. Users do not have privileges until they are specified by a DBA.
If no users have been created —The Progress 4GL interface will not display a logon dialog box, but the OpenEdge SQL interface will. Anything may be entered in the user identification field and the password field may be left blank.
