Determine the privileges of the blank user ID
- Last Updated:Mar 30, 2020
- 2 minute read
- OpenEdge
- Version 12.2
- Documentation
By not specifying the User ID (-U
)
and Password (-P
) connection parameters when connecting
to a database (at startup or in the CONNECT
statement),
the user can access the database with a default user identity that
has the blank user ID or the OS process user ID.
You can
also authenticate a blank (""
) user ID for a database
connection by connecting to a database (at startup or in the CONNECT
statement)
with the User ID (-U
) and Password (-P
)
connection parameters with no value specified for -U
,
or by using an ABL function or method like SET-DB-CLIENT
()
to explicitly set a blank user identity for an existing
database connection.
For more information on these connection parameters and ABL functions and methods for setting database connection identity, see Learn about Identity Management and OpenEdge Programming Interfaces.
Any user can use OpenEdge or an OpenEdge application with a blank user ID and access tables and fields in the database as long as the following conditions are all met:
- The database is configured to allow blank user ID connections (the default)
- The table- and field-level permissions permit it (blank user ID) (the default)
- The procedures being run are precompiled with table/field access authorized
As the security administrator, you can deny privileges to the blank user ID to ensure that users with blank user ID do not gain access to the data by following these steps.
To restrict blank user ID access privileges: