How to re-activate Blank Userid Access ? - Progress Community

Loading

Skip to Main Content

How to re-activate Blank Userid Access ?

Apart from dumping and loading the database to a new structure, one possibility is to use a 4GL query to alter the security settings in the hidden metaschema tables. Please note that this is not supported by Progress Software.

Mar 14, 2016
Knowledge

Title

How to re-activate Blank Userid Access ?

URL Name

P24078

Article Number

000149903

Environment

Product: Progress OpenEdge Version: All supported versions OS: All supported platforms

Question/Problem Description

How to re-activate Blank Userid Access ?
How to revert "Disallow Blank Userid Access" (compile-time) security ?
I chose to disallow blank userid access to my database, but changed my mind.
4GL/ABL: Is it possible to reverse or deactivate the database 'Disallow Blank Userid Access' Security setting programmatically?
How to allow Database Blank Userid Access using 4GL/ABL after it has been set to 'Disallow Blank Userid Access'?
How to provide only read access to the blank userid's ?
Logging in as a blank user and generating reports via the data dictionary returns error "You do not have permission to select tables"

Steps to Reproduce

Clarifying Information

Admin > Security > Disallow Blank Userid Access

Error Message

Defect Number

Enhancement Number

Cause

Resolution

There is no direct way (menu, button, option) to re-activate Blank Userid Access (compile-time) security.

Apart from dumping and loading the database to a new structure, 4GL code to alter compile time security settings in the hidden metaschema tables can be considered as an alternative. Please note that making modificationt through the metaschema is not supported by Progress Software. If you choose to attempt this, please backup the database before running the code below.

Versions earlier than Progress 9:

FOR EACH _file WHERE:
    ASSIGN _file._CAN-READ = "*"
                   _file._CAN-WRITE = "*"
                   _file._CAN-CREATE = "*"
                   _file._CAN-DELETE = "*".
END.

Progress 9 or later:

FOR EACH _file WHERE _file-num > 0 AND _owner = "PUB":
    ASSIGN _file._CAN-READ = "*"
                   _file._CAN-WRITE = "*"
                   _file._CAN-CREATE = "*"
                   _file._CAN-DELETE = "*".
END.

To provide only read access to the tables and data for blank userid's execute the following code after enabling "Disallow Blank UserID" from Admin > Security.

FOR EACH _file WHERE _file-num > 0 AND _owner = "PUB":
    ASSIGN _file._CAN-READ = "*".
END.

The "disable blank userid access" action puts a "!" in the can-read, can-write, can-create, and can-delete fields of the _file table for your database tables. This character means "no blank users have access to them"

The above query modifies the table security back to "enabled to all" by replacing the "!" with "*". If some level of security (user access) implemented within your database, replace "*" with the appropriate string of users that have compile-time security.

Workaround

Notes

Progress Article:

What is the difference between Disallow Blank User (compile-time) security and Disallow Blank User (run-time) security?

Keyword Phrase

Last Modified Date

11/6/2023 3:25 PM

OpenEdge General DiscussionsOpenEdge DeploymentOpenEdge DevelopmentOpenEdge RDBMSOpenEdge ArchitectureOpenEdge Pro2

Drop Files

Upload FilesOr drop 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.

Loading

How to re-activate Blank Userid Access ? - Progress Community