[DERBY-1711] In an embedded env, connection happens properly even when the password supplied is wrong.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Invalid
• Affects Version/s: 10.1.3.1
• Component/s: JDBC
• Environment: Win XP,Java 1.4.x
• Assignee: Unassigned
• Reporter: Chinmay Bajikar
• Created: 17/Aug/06 07:59
• Updated: 07/Sep/06 01:16
• Resolved: 07/Sep/06 01:16

Description

Hi,
I am a new user of Derby.
Have tried to set user authorization at the database level using the example given in the Derby Dev Guide.(Page 85).
The steps that I do are as follows,
1)Create a db (using create=true attribute in the connection url)
2) Connect to the db and set the appropriate properties i.e. set requireAuthentication to true,provider to builtin, add a new user,passwrd and give it full access.
3) Set the default access level to noAccess.
4) Close this connection.
5) Now make a new connection using the user name/passwd.It connects fine.
6) Now try to make a new connection using a wrong user name and it gives a Connection Refused exception.
7) Finally try giving a right username and wrong passwd and the connection still happens.

Have attached the source file which does all these above steps for reproducing the issue.

Thanks,
Chinmay.