[
https://issues.apache.org/jira/browse/DERBY-4821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12915673#action_12915673
]
Knut Anders Hatlen commented on DERBY-4821:
-------------------------------------------
No password was required before authentication was enabled, so it wouldn't
complain when the password attribute was missing. IJ checks the URL and warns
about unknown attributes, but that's only implemented for the embedded driver
for now. There is an open improvement request for getting these warnings with
the client driver too - DERBY-2697.
> After a shutdown and startup, unable to connect. ij\jdbc returns an
> authentication failure due to invalid username\password.
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-4821
> URL: https://issues.apache.org/jira/browse/DERBY-4821
> Project: Derby
> Issue Type: Bug
> Components: Network Server
> Affects Versions: 10.5.3.0, 10.6.1.0
> Environment: windows server 2003, java 6.0.20/18
> Reporter: Yacov M
> Priority: Blocker
>
> I created a database using the following script:
> connect
> 'jdbc:derby://localhost:1527/Tasks;create=true;user=someuser;passsword=somepassword';
> CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY('derby.user.someuser',
> 'somepassword');
> CALL
> SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY('derby.authentication.provider','BUILTIN');
> CALL
> SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY('derby.connection.requireAuthentication',
> 'true');
> as long as the database isn't shutdown (I'm performing a clean shutdown,
> using the java API NetworkServerControl shutdown method), I'm able to connect
> to the database using the user 'someuser'.
> But after i boot the database after a shutdown, every connection attempt via
> IJ.bat (or via jdbc) is failing.
> for example, IJ.bat output:
> ij> connect
> 'jdbc:derby://localhost:1527/Tasks;user=someuser;passsword=somepassword';
> ERROR 08004: Connection authentication failure occurred. Reason: userid or
> password invalid.
> Anyone got any ideas?
> Thanks in advance!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
