[#DERBY-198] Add Support for network Server USRIDONL security

Derby

Add Support for network Server USRIDONL security

Created: 05/Apr/05 08:11 AM Updated: 05/Jun/05 01:44 AM

Return to search

Component/s:

Network Server

Affects Version/s:

10.1.1.0

Fix Version/s:

10.1.1.0

Time Tracking:

Not Specified

File Attachments:

	File Name	Date Attached	Attached By	Size
	Derby198.diff	2005-04-07 10:01 PM	Sunitha Kambhampati	25 kB

Resolution Date:

01/Jun/05 04:17 AM

Description

« Hide

Currently Network Server supports only two security mechanisms.

User ID and password (usridpwd)
User ID and encrypted password (eusridpwd)

It would be good to add support for User ID Only security so that it could more closely match the embedded driver and not always require a password.

See details of security mechanism implementations in section 4.4.2.1 of

DRDA V3 Vol. 1: Distributed Relational Database Architecture
http://www.opengroup.org/dbiop/

All

Comments

Work Log

Change History

Subversion Commits

Sort Order:

[ Permlink | « Hide ]

Sunitha Kambhampati added a comment - 07/Apr/05 10:01 PM

Patch to support USRIDONL security for network server. derbynetmats tests ran fine. Added new tests to test security mechanism.

[ Permlink | « Hide ]

Kathey Marsden added a comment - 08/Apr/05 04:14 AM

Committed revision 160439 for this patch.
Ran derbynetmats on the change.

[ Permlink | « Hide ]

Sunitha Kambhampati added a comment - 01/Jun/05 04:17 AM

This fix was committed with revision 160439 a while ago.
_________

The general flow is
client sends ACCSEC with CodePoint.SECMEC as SECMEC_USRIDONL (4) to use userid only security.
In the ACCSECRD the server sends secmec as SECMEC_USRIDONL which means it supports this security mechanism
Then client sends SECCHK sending only USRID
The server sends a SECCHKRM as normal after validating the userid. This is actually done by trying to obtain a connection from the database.

Changes that went in
-- Recognize CodePoint.SECMEC_USRIDONL sent in for CodePoint.SECMEC as part of the ACCSEC command (DRDAConnThread#parseACCSEC)
-- validate if the right parameters are sent for SECMEC_USRIDONL
-- Change the constant SECCHKCD_SECTKNMISSING to SECCHKCD_SECTKNMISSING_OR_INVALID for clarity. Since this code is sent in cases when the security token is invalid as well as when it is missing.
-- Changes to parseSECCHK to check for only the userid to support SECMEC_USRIDONL
-- Changes to Database#makeConnection to take care of a null password