Feedback
Did this article resolve your question/issue?

   

Article

OpenEdge SQL92 Authentication

« Go Back

Information

 
TitleOpenEdge SQL92 Authentication
URL NameOpenEdge-SQL92-Authentication
Article Number000203108
EnvironmentProduct: Progress
Product: OpenEdge
Version: 9.x, 10.x, 11.x, 12.x
OS: All supported platforms
Other: SQL92
Question/Problem Description
OpenEdge SQL92 Authentication
When is an authentication check made when connecting to SQL92?
Steps to Reproduce
Clarifying Information
Error Message
Defect Number
Enhancement Number
Cause
Resolution
In a database where no users have been created within the database _user table no password is necessary to connect to the database.
Any text value may be supplied for the password and the connection to the database would be allowed because there is no authentication check at this time.

Authentication is only enabled when users are created in the _user table.  If there are no users in the database, there is no authentication check performed when connecting. However, if a user other than the DBA connects, this user has access only to public tables or tables where a DBA has granted privileges to the user.

NOTE: Privileges can be granted even when there are no users created in the database. If users are added to the _user table they must be granted privileges from the SQL side by a DBA account in order to work with data from the SQL side. Failure to do so will result in queries returning error 7512.  

To enable Authentication, create at least one user in the database.
Always grant DBA access to at least one user of the database.  

When users are created in the database, the default DBA (the user who created the database) becomes  disabled. It is important to grant DBA access to at least one user so you will have a valid DBA account.  

In the event that at least one user was created but DBA access rights are not given, this user can create a sysprogress user via the 4GL Data Administration Tool to allow DBA access to the database.  

Make sure that password is defined for sysprogress user or connection will fail.
Workaround
Notes
Last Modified Date5/30/2021 7:00 PM
Attachment 
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.