Documentation states Disallow Blank UserId Connections doesn't work in all scenarios

The OpenEdge Data Management: Database Administration Chapter 8: Maintaining Security documentation states that the option "Disallow Blank UserId Connections" works, "but not all, scenarios". It doesn't explain what these scenarios are, so this should be explained or this statement in the documentation should be removed.

The passage in the documentation is:

"Caution: If a user connects to a database with the default blank user identity, the user potentially has full access to the database. You can prevent users with a blank user ID from gaining unauthorized access to an OpenEdge database in two ways: 1) setting a database option to Disallow Blank UserId Connections, in which case the User ID (-U) parameter and a non-blank user ID are required to connect to the database, or 2) setting the security option to Disallow Blank Userid Access. The first option prevents blank users from connecting to the database in certain, but not all, scenarios; the second option prevents blank users from accessing any data in the database by explicitly revoking blank user ID access to all data in the database, and provides the most comprehensive protection from unauthorized access by a blank user. Also, remember to assign non-blank user IDs to the security administrator role before restricted access for blank users."

The exact cause is not known at this time.  A documentation bug has been logged to clarify or remove this statement.  
 

None at this time.
 

References to Other Documentation:
OpenEdge Data Management: Database Administration, Chapter 8: Maintaining Security