[
https://issues.apache.org/jira/browse/DERBY-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12520323
]
Rick Hillegas commented on DERBY-1387:
--------------------------------------
I see. So if the DBA uses system procedures to read the passwords, hashed
values come back.
Starting another thread on this topic: Password management is generally handled
by end-users. An administrator sets up an initial password and the end-user
then changes it immediately afterward. I don't think our BUILTIN scheme works
this way--although we could improve it by giving end-users a tool to change
their passwords. The JMX-based password setting could be useful if we just see
it as a way for the DBA to initialize passwords or forcibly reset them when the
user forgets her credentials.
> Add JMX extensions to Derby
> ---------------------------
>
> Key: DERBY-1387
> URL: https://issues.apache.org/jira/browse/DERBY-1387
> Project: Derby
> Issue Type: New Feature
> Components: Services
> Reporter: Sanket Sharma
> Assignee: Bernt M. Johnsen
> Attachments: DERBY-1387-1.diff, DERBY-1387-1.stat, DERBY-1387-2.diff,
> DERBY-1387-2.stat, DERBY-1387-3.diff, DERBY-1387-3.stat, derbyjmx.patch,
> jmx.diff, jmx.stat, jmxFuncspec.html, Requirements for JMX Updated.html,
> Requirements for JMX.html, Requirements for JMX.zip
>
>
> This is a draft requirement specification for adding monitoring and
> management extensions to Apache Derby using JMX. The requirements document
> has been uploaded on JIRA as well as the Derby Wiki page at
> http://wiki.apache.org/db-derby/_Requirement_Specifications_for_Monitoring_%26_Management_Extensions_using_JMX
> Developers and Users are requested to please look at the document (feature
> list in particular) and add their own rating to features by adding a coloumn
> to the table.
> Comments are welcome.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
