[
https://issues.apache.org/jira/browse/DERBY-4579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12858703#action_12858703
]
Knut Anders Hatlen commented on DERBY-4579:
-------------------------------------------
Hi Kim. Thanks for picking up this issue.
> Which is the case for this property? I'm guessing it takes effect
> immediately, but I want to make sure.
Yes, the changes take effect immediately.
> I'm not aware of a NONE scheme; for the
> derby.authentication.provider property the possibilities are LDAP,
> BUILTIN, and a Java class name, which I thought also indicated the
> use of an external authentication scheme.
You're right, NONE isn't mentioned in the documentation. There is a
no-op authentication service implementation class called
NoneAuthenticationServiceImpl, and it's sometimes referred to as NONE
in code comments. This is the authentication service that's used when
authentication is disabled. I guess it's clearer if we say
"authentication disabled" instead of "the NONE authentication
service"...
> So is it only BUILTIN that you can use strong password substitution
> with?
It is possible to use strong password substitution with (old) BUILTIN
and when authentication is turned off. Using password substitution
when authentication is turned off may perhaps not make much sense, but
it is possible (you can specify user name and password when
authentication is disabled, and they will be sent to the server, they
just won't be checked).
Hope this made things clearer.
> Document the configurable hash authentication scheme
> ----------------------------------------------------
>
> Key: DERBY-4579
> URL: https://issues.apache.org/jira/browse/DERBY-4579
> Project: Derby
> Issue Type: Improvement
> Components: Documentation
> Affects Versions: 10.6.0.0
> Reporter: Knut Anders Hatlen
> Assignee: Kim Haase
>
> DERBY-4483 adds the ability to configure which message digest algorithm to
> use to protect the passwords that are stored in the database when using
> BUILTIN authentication.
> I think these changes are required:
> * Reference manual: Document the new database property
> derby.authentication.builtin.algorithm. It's a dynamic property that can be
> set either on database level or on system level. Its value is the name of a
> message digest algorithm available from one of the Java Cryptography
> Extension providers registered in the JVM. Example values: MD5, SHA-256,
> SHA-512. The specified algorithm will be applied on the concatenation of the
> user name and the password before it's stored in the database. If the
> property is NULL or the empty string, the old algorithm (SHA-1 on the
> password only) is applied instead.
> * Developer's guide: Mention the property in "List of user authentication
> properties"
> * Server and admin guide: In the table in section "Network client security",
> mention that strong password substitution cannot be used to connect as a user
> whose password has been stored with the new scheme. I'd suggest changing the
> following sentence:
> Strong password substitution cannot be used with external Derby
> authentication schemes (for example, LDAP).
> And replacing it with something like:
> Strong password substitution can only be used with Derby's NONE and
> BUILTIN authentication schemes. Also, for the BUILTIN scheme, it does not
> work for database-level users whose password has been protected by a custom
> message digest algorithm specified by the
> derby.authentication.builtin.algorithm property.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
