[DERBY-928] Add ability to network server to accept connections with a certain security mechanism.

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 10.2.1.6
• Component/s: Network Server
• Assignee: Sunitha Kambhampati
• Reporter: Sunitha Kambhampati
• Created: 07/Feb/06 09:41
• Updated: 01/Jul/09 00:34
• Resolved: 01/Mar/06 23:29

Description

Currently the network server has support for the following security mechanisms
1) USRIDONL (userid only),
2) USRIDPWD (clear text userid and password),
3) EUSRIDPWD (encrypted userid and password).

Thus the #3 encrypted userid and password security mechanism is secure with respect to the userid/password sent across the wire. Currently there is no way to setup the network server to ensure that it accepts connections coming in at a certain security mechanism. It seems reasonable & useful to have a server want to accept connections from clients with a particular security mechanism (e.g lets say encrypted userid/password and reject usridpwd ie clear text userid and password)

This jira will add support for this by adding a property to enable the server to be able to accept connections from clients with a certain security mechanism.
--------------------
I actually couldnt find if a rank was given to the security mechanisms in the drda spec. If it were so, then maybe a property for setting the minimum security mechanism accepted by the server would be appropriate.

Issue Links

• incorporates: DERBY-1682 Add documentation for derby.drda.securityMechanism.