Details
-
Bug
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
10.1.1.0, 10.1.2.1, 10.1.3.1, 10.2.1.6, 10.2.2.0, 10.3.1.4
-
None
-
Normal
Description
There is a couple of issues with the paragraph/section "User authentication and authorization extended examples" in the developer's guide
http://db.apache.org/derby/docs/10.2/devguide/rdevcsecure26537.html
1) The methods turnOnBuiltInUsers() & turnOffBuiltInUsers() do NOT shutdown and reboot the database for which the 'derby.connection.requireAuthentication' authentication database property is being set - as this last one is a derby static property, it will not be taken into account until the database is rebooted (or the whole derby engine instance). Hence, the 2 checks for "Confirming requireAuthentication" is misleading as the property value is changed but the actual database authentication enabling/disabling has not changed since it was last booted. Database needs to be shutdown and rebooted after 'derby.connection.requireAuthentication' is set and then some negative testing of invalid user connection needs to be added to show that only valid users can connect (in the case, authentication is being enabled).
2) Paragraph (extended examples section) also needs to be moved at the same level as the 2 above such as:
"User authentication example in a single-user, embedded environment"
http://db.apache.org/derby/docs/10.2/devguide/rdevcsecure125.html
"User authentication example in a client/server environment"
http://db.apache.org/derby/docs/10.2/devguide/rdevcsecure13713.html
since the extended examples (once fixed - see 1)) can be applied in both a client-server and embedded environments context.
Attachments
Attachments
Issue Links
- is depended upon by
-
DERBY-3200 Developer's Guide: Add examples showing use of SQL authorization with user authentication
-
- Closed
-