You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Sunitha Kambhampati (JIRA)" <de...@db.apache.org> on 2006/08/12 01:03:14 UTC
[jira] Created: (DERBY-1682) Add documentation for
derby.drda.securityMechanism.
Add documentation for derby.drda.securityMechanism.
---------------------------------------------------
Key: DERBY-1682
URL: http://issues.apache.org/jira/browse/DERBY-1682
Project: Derby
Issue Type: Task
Components: Documentation
Reporter: Sunitha Kambhampati
Priority: Minor
Fix For: 10.2.0.0
Under section Setting Network Server properties
http://db.apache.org/derby/docs/dev/adminguide/tadminconfigsettingnetwrokserverproperties.html
Add this new property
derby.drda.securityMechanism
Restricts client connections based on the security mechanism.
if derby.drda.securityMechanism is set to a valid mechanism, then
the Network Server accepts only connections which use that
security mechanism. No other types of connections are accepted.
if the derby.drda.securityMechanism is not set at all, then the
Network Server accepts any connection which uses a valid
security mechanism.
Syntax:
derby.drda.securityMechanism=[USER_ONLY_SECURITY|CLEAR_TEXT_PASSWORD_SECURITY|ENCRYPTED_USER_AND_PASSWORD_SECURITY]
Example:
derby.drda.securityMechanism=USER_ONLY_SECURITY
The server running with this property will only accept client connections with USER_ONLY_SECURITY.
Static or Dynamic:
This property is static. Server must be restarted for the property to take effect.
Default value for this property is as though it is not set - in which case
the server will allow clients with supported security mechanisms to connect
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [jira] Updated: (DERBY-1682) Add documentation for
derby.drda.securityMechanism.
Posted by Kim Haase <Ca...@Sun.COM>.
Thanks very much, Laura. I'll follow this advice.
Kim
Laura Stewart wrote On 09/01/06 13:40,:
> It is my understanding that each updated patch should have it's own
> name. You use dates, I use one up numbers... as long as it it clear
> to the committer. It is also good practice to mention in your comment
> the name of the patch. While the email thread adds it automatically,
> the comments in JIRA do not.
>
> On 9/1/06, Kim Haase (JIRA) <de...@db.apache.org> wrote:
>
>> [ http://issues.apache.org/jira/browse/DERBY-1682?page=all ]
>>
>>Kim Haase updated DERBY-1682:
>>-----------------------------
>>
>> Attachment: radmindrdasecmechanism090106.html
>>
>>I'm sorry -- I copied it from the wrong workspace. See radmindrdasecmechanism090106.html. By the way, am I doing the right thing in giving each corrected patch or file a new name, or should I just be overwriting the bad one with the corrected one? Thanks!
>>
>>
>>>Add documentation for derby.drda.securityMechanism.
>>>---------------------------------------------------
>>>
>>> Key: DERBY-1682
>>> URL: http://issues.apache.org/jira/browse/DERBY-1682
>>> Project: Derby
>>> Issue Type: Task
>>> Components: Documentation
>>> Reporter: Sunitha Kambhampati
>>> Assigned To: Laura Stewart
>>> Priority: Minor
>>> Fix For: 10.3.0.0
>>>
>>> Attachments: derby1682_083106.diff, derby1682_adminguide.diff, derby1682_update.diff, radmindrdasecmechanism.html, radmindrdasecmechanism090106.html, radmindrdasecmechanism_083106.html, radmindrdasecmechanism_update.html
>>>
>>>
>>>Under section Setting Network Server properties
>>>http://db.apache.org/derby/docs/dev/adminguide/tadminconfigsettingnetwrokserverproperties.html
>>>Add this new property
>>>derby.drda.securityMechanism
>>>Restricts client connections based on the security mechanism.
>>>if derby.drda.securityMechanism is set to a valid mechanism, then
>>>the Network Server accepts only connections which use that
>>>security mechanism. No other types of connections are accepted.
>>>if the derby.drda.securityMechanism is not set at all, then the
>>>Network Server accepts any connection which uses a valid
>>>security mechanism.
>>>Syntax:
>>>derby.drda.securityMechanism=[USER_ONLY_SECURITY|CLEAR_TEXT_PASSWORD_SECURITY|ENCRYPTED_USER_AND_PASSWORD_SECURITY]
>>>Example:
>>>derby.drda.securityMechanism=USER_ONLY_SECURITY
>>>The server running with this property will only accept client connections with USER_ONLY_SECURITY.
>>>Static or Dynamic:
>>>This property is static. Server must be restarted for the property to take effect.
>>>Default value for this property is as though it is not set - in which case
>>>the server will allow clients with supported security mechanisms to connect
>>
>>--
>>This message is automatically generated by JIRA.
>>-
>>If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
>>-
>>For more information on JIRA, see: http://www.atlassian.com/software/jira
>>
>>
>>
>
>
>
Re: [jira] Updated: (DERBY-1682) Add documentation for derby.drda.securityMechanism.
Posted by Laura Stewart <sc...@gmail.com>.
It is my understanding that each updated patch should have it's own
name. You use dates, I use one up numbers... as long as it it clear
to the committer. It is also good practice to mention in your comment
the name of the patch. While the email thread adds it automatically,
the comments in JIRA do not.
On 9/1/06, Kim Haase (JIRA) <de...@db.apache.org> wrote:
> [ http://issues.apache.org/jira/browse/DERBY-1682?page=all ]
>
> Kim Haase updated DERBY-1682:
> -----------------------------
>
> Attachment: radmindrdasecmechanism090106.html
>
> I'm sorry -- I copied it from the wrong workspace. See radmindrdasecmechanism090106.html. By the way, am I doing the right thing in giving each corrected patch or file a new name, or should I just be overwriting the bad one with the corrected one? Thanks!
>
> > Add documentation for derby.drda.securityMechanism.
> > ---------------------------------------------------
> >
> > Key: DERBY-1682
> > URL: http://issues.apache.org/jira/browse/DERBY-1682
> > Project: Derby
> > Issue Type: Task
> > Components: Documentation
> > Reporter: Sunitha Kambhampati
> > Assigned To: Laura Stewart
> > Priority: Minor
> > Fix For: 10.3.0.0
> >
> > Attachments: derby1682_083106.diff, derby1682_adminguide.diff, derby1682_update.diff, radmindrdasecmechanism.html, radmindrdasecmechanism090106.html, radmindrdasecmechanism_083106.html, radmindrdasecmechanism_update.html
> >
> >
> > Under section Setting Network Server properties
> > http://db.apache.org/derby/docs/dev/adminguide/tadminconfigsettingnetwrokserverproperties.html
> > Add this new property
> > derby.drda.securityMechanism
> > Restricts client connections based on the security mechanism.
> > if derby.drda.securityMechanism is set to a valid mechanism, then
> > the Network Server accepts only connections which use that
> > security mechanism. No other types of connections are accepted.
> > if the derby.drda.securityMechanism is not set at all, then the
> > Network Server accepts any connection which uses a valid
> > security mechanism.
> > Syntax:
> > derby.drda.securityMechanism=[USER_ONLY_SECURITY|CLEAR_TEXT_PASSWORD_SECURITY|ENCRYPTED_USER_AND_PASSWORD_SECURITY]
> > Example:
> > derby.drda.securityMechanism=USER_ONLY_SECURITY
> > The server running with this property will only accept client connections with USER_ONLY_SECURITY.
> > Static or Dynamic:
> > This property is static. Server must be restarted for the property to take effect.
> > Default value for this property is as though it is not set - in which case
> > the server will allow clients with supported security mechanisms to connect
>
> --
> This message is automatically generated by JIRA.
> -
> If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
> -
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
>
>
--
Laura Stewart
[jira] Reopened: (DERBY-1682) Add documentation for
derby.drda.securityMechanism.
Posted by "Kim Haase (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1682?page=all ]
Kim Haase reopened DERBY-1682:
------------------------------
I'll provide a patch file to add the new security mechanism.
> Add documentation for derby.drda.securityMechanism.
> ---------------------------------------------------
>
> Key: DERBY-1682
> URL: http://issues.apache.org/jira/browse/DERBY-1682
> Project: Derby
> Issue Type: Task
> Components: Documentation
> Reporter: Sunitha Kambhampati
> Assigned To: Laura Stewart
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby1682_adminguide.diff, radmindrdasecmechanism.html
>
>
> Under section Setting Network Server properties
> http://db.apache.org/derby/docs/dev/adminguide/tadminconfigsettingnetwrokserverproperties.html
> Add this new property
> derby.drda.securityMechanism
> Restricts client connections based on the security mechanism.
> if derby.drda.securityMechanism is set to a valid mechanism, then
> the Network Server accepts only connections which use that
> security mechanism. No other types of connections are accepted.
> if the derby.drda.securityMechanism is not set at all, then the
> Network Server accepts any connection which uses a valid
> security mechanism.
> Syntax:
> derby.drda.securityMechanism=[USER_ONLY_SECURITY|CLEAR_TEXT_PASSWORD_SECURITY|ENCRYPTED_USER_AND_PASSWORD_SECURITY]
> Example:
> derby.drda.securityMechanism=USER_ONLY_SECURITY
> The server running with this property will only accept client connections with USER_ONLY_SECURITY.
> Static or Dynamic:
> This property is static. Server must be restarted for the property to take effect.
> Default value for this property is as though it is not set - in which case
> the server will allow clients with supported security mechanisms to connect
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-1682) Add documentation for
derby.drda.securityMechanism.
Posted by "Kim Haase (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1682?page=all ]
Kim Haase updated DERBY-1682:
-----------------------------
Attachment: radmindrdasecmechanism090106.html
I'm sorry -- I copied it from the wrong workspace. See radmindrdasecmechanism090106.html. By the way, am I doing the right thing in giving each corrected patch or file a new name, or should I just be overwriting the bad one with the corrected one? Thanks!
> Add documentation for derby.drda.securityMechanism.
> ---------------------------------------------------
>
> Key: DERBY-1682
> URL: http://issues.apache.org/jira/browse/DERBY-1682
> Project: Derby
> Issue Type: Task
> Components: Documentation
> Reporter: Sunitha Kambhampati
> Assigned To: Laura Stewart
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby1682_083106.diff, derby1682_adminguide.diff, derby1682_update.diff, radmindrdasecmechanism.html, radmindrdasecmechanism090106.html, radmindrdasecmechanism_083106.html, radmindrdasecmechanism_update.html
>
>
> Under section Setting Network Server properties
> http://db.apache.org/derby/docs/dev/adminguide/tadminconfigsettingnetwrokserverproperties.html
> Add this new property
> derby.drda.securityMechanism
> Restricts client connections based on the security mechanism.
> if derby.drda.securityMechanism is set to a valid mechanism, then
> the Network Server accepts only connections which use that
> security mechanism. No other types of connections are accepted.
> if the derby.drda.securityMechanism is not set at all, then the
> Network Server accepts any connection which uses a valid
> security mechanism.
> Syntax:
> derby.drda.securityMechanism=[USER_ONLY_SECURITY|CLEAR_TEXT_PASSWORD_SECURITY|ENCRYPTED_USER_AND_PASSWORD_SECURITY]
> Example:
> derby.drda.securityMechanism=USER_ONLY_SECURITY
> The server running with this property will only accept client connections with USER_ONLY_SECURITY.
> Static or Dynamic:
> This property is static. Server must be restarted for the property to take effect.
> Default value for this property is as though it is not set - in which case
> the server will allow clients with supported security mechanisms to connect
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-1682) Add documentation for
derby.drda.securityMechanism.
Posted by "Kim Haase (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1682?page=comments#action_12430263 ]
Kim Haase commented on DERBY-1682:
----------------------------------
Should the additional security mechanism STRONG_PASSWORD_SUBSTITUTE_SECURITY be added to the syntax in radmindrdasecmechanism.dita? (See DERBY-1747.) Francois Orsini should probably answer this question.
> Add documentation for derby.drda.securityMechanism.
> ---------------------------------------------------
>
> Key: DERBY-1682
> URL: http://issues.apache.org/jira/browse/DERBY-1682
> Project: Derby
> Issue Type: Task
> Components: Documentation
> Reporter: Sunitha Kambhampati
> Assigned To: Laura Stewart
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby1682_adminguide.diff, radmindrdasecmechanism.html
>
>
> Under section Setting Network Server properties
> http://db.apache.org/derby/docs/dev/adminguide/tadminconfigsettingnetwrokserverproperties.html
> Add this new property
> derby.drda.securityMechanism
> Restricts client connections based on the security mechanism.
> if derby.drda.securityMechanism is set to a valid mechanism, then
> the Network Server accepts only connections which use that
> security mechanism. No other types of connections are accepted.
> if the derby.drda.securityMechanism is not set at all, then the
> Network Server accepts any connection which uses a valid
> security mechanism.
> Syntax:
> derby.drda.securityMechanism=[USER_ONLY_SECURITY|CLEAR_TEXT_PASSWORD_SECURITY|ENCRYPTED_USER_AND_PASSWORD_SECURITY]
> Example:
> derby.drda.securityMechanism=USER_ONLY_SECURITY
> The server running with this property will only accept client connections with USER_ONLY_SECURITY.
> Static or Dynamic:
> This property is static. Server must be restarted for the property to take effect.
> Default value for this property is as though it is not set - in which case
> the server will allow clients with supported security mechanisms to connect
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-1682) Add documentation for
derby.drda.securityMechanism.
Posted by "Laura Stewart (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1682?page=all ]
Laura Stewart updated DERBY-1682:
---------------------------------
Attachment: derby1682_adminguide.diff
radmindrdasecmechanism.html
Attached the new file to document the securityMechinism property.
Please review and comment.
> Add documentation for derby.drda.securityMechanism.
> ---------------------------------------------------
>
> Key: DERBY-1682
> URL: http://issues.apache.org/jira/browse/DERBY-1682
> Project: Derby
> Issue Type: Task
> Components: Documentation
> Reporter: Sunitha Kambhampati
> Assigned To: Laura Stewart
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby1682_adminguide.diff, radmindrdasecmechanism.html
>
>
> Under section Setting Network Server properties
> http://db.apache.org/derby/docs/dev/adminguide/tadminconfigsettingnetwrokserverproperties.html
> Add this new property
> derby.drda.securityMechanism
> Restricts client connections based on the security mechanism.
> if derby.drda.securityMechanism is set to a valid mechanism, then
> the Network Server accepts only connections which use that
> security mechanism. No other types of connections are accepted.
> if the derby.drda.securityMechanism is not set at all, then the
> Network Server accepts any connection which uses a valid
> security mechanism.
> Syntax:
> derby.drda.securityMechanism=[USER_ONLY_SECURITY|CLEAR_TEXT_PASSWORD_SECURITY|ENCRYPTED_USER_AND_PASSWORD_SECURITY]
> Example:
> derby.drda.securityMechanism=USER_ONLY_SECURITY
> The server running with this property will only accept client connections with USER_ONLY_SECURITY.
> Static or Dynamic:
> This property is static. Server must be restarted for the property to take effect.
> Default value for this property is as though it is not set - in which case
> the server will allow clients with supported security mechanisms to connect
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (DERBY-1682) Add documentation for
derby.drda.securityMechanism.
Posted by "Jean T. Anderson (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1682?page=all ]
Jean T. Anderson resolved DERBY-1682.
-------------------------------------
Fix Version/s: 10.3.0.0
(was: 10.2.1.0)
Resolution: Fixed
Derby Info: (was: [Patch Available])
Committed patch derby1682_adminguide.diff to trunk, revision 434218.
> Add documentation for derby.drda.securityMechanism.
> ---------------------------------------------------
>
> Key: DERBY-1682
> URL: http://issues.apache.org/jira/browse/DERBY-1682
> Project: Derby
> Issue Type: Task
> Components: Documentation
> Reporter: Sunitha Kambhampati
> Assigned To: Laura Stewart
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby1682_adminguide.diff, radmindrdasecmechanism.html
>
>
> Under section Setting Network Server properties
> http://db.apache.org/derby/docs/dev/adminguide/tadminconfigsettingnetwrokserverproperties.html
> Add this new property
> derby.drda.securityMechanism
> Restricts client connections based on the security mechanism.
> if derby.drda.securityMechanism is set to a valid mechanism, then
> the Network Server accepts only connections which use that
> security mechanism. No other types of connections are accepted.
> if the derby.drda.securityMechanism is not set at all, then the
> Network Server accepts any connection which uses a valid
> security mechanism.
> Syntax:
> derby.drda.securityMechanism=[USER_ONLY_SECURITY|CLEAR_TEXT_PASSWORD_SECURITY|ENCRYPTED_USER_AND_PASSWORD_SECURITY]
> Example:
> derby.drda.securityMechanism=USER_ONLY_SECURITY
> The server running with this property will only accept client connections with USER_ONLY_SECURITY.
> Static or Dynamic:
> This property is static. Server must be restarted for the property to take effect.
> Default value for this property is as though it is not set - in which case
> the server will allow clients with supported security mechanisms to connect
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-1682) Add documentation for
derby.drda.securityMechanism.
Posted by "Kim Haase (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1682?page=all ]
Kim Haase updated DERBY-1682:
-----------------------------
Derby Info: [Patch Available]
> Add documentation for derby.drda.securityMechanism.
> ---------------------------------------------------
>
> Key: DERBY-1682
> URL: http://issues.apache.org/jira/browse/DERBY-1682
> Project: Derby
> Issue Type: Task
> Components: Documentation
> Reporter: Sunitha Kambhampati
> Assigned To: Laura Stewart
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby1682_adminguide.diff, derby1682_update.diff, radmindrdasecmechanism.html, radmindrdasecmechanism_update.html
>
>
> Under section Setting Network Server properties
> http://db.apache.org/derby/docs/dev/adminguide/tadminconfigsettingnetwrokserverproperties.html
> Add this new property
> derby.drda.securityMechanism
> Restricts client connections based on the security mechanism.
> if derby.drda.securityMechanism is set to a valid mechanism, then
> the Network Server accepts only connections which use that
> security mechanism. No other types of connections are accepted.
> if the derby.drda.securityMechanism is not set at all, then the
> Network Server accepts any connection which uses a valid
> security mechanism.
> Syntax:
> derby.drda.securityMechanism=[USER_ONLY_SECURITY|CLEAR_TEXT_PASSWORD_SECURITY|ENCRYPTED_USER_AND_PASSWORD_SECURITY]
> Example:
> derby.drda.securityMechanism=USER_ONLY_SECURITY
> The server running with this property will only accept client connections with USER_ONLY_SECURITY.
> Static or Dynamic:
> This property is static. Server must be restarted for the property to take effect.
> Default value for this property is as though it is not set - in which case
> the server will allow clients with supported security mechanisms to connect
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-1682) Add documentation for
derby.drda.securityMechanism.
Posted by "Laura Stewart (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1682?page=comments#action_12432002 ]
Laura Stewart commented on DERBY-1682:
--------------------------------------
Kim, when I look at the html file, it doesn't appear any different than the one before...
The diff file seems to have the corrections though. Can you double check the html file that you attached?
> Add documentation for derby.drda.securityMechanism.
> ---------------------------------------------------
>
> Key: DERBY-1682
> URL: http://issues.apache.org/jira/browse/DERBY-1682
> Project: Derby
> Issue Type: Task
> Components: Documentation
> Reporter: Sunitha Kambhampati
> Assigned To: Laura Stewart
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby1682_083106.diff, derby1682_adminguide.diff, derby1682_update.diff, radmindrdasecmechanism.html, radmindrdasecmechanism_083106.html, radmindrdasecmechanism_update.html
>
>
> Under section Setting Network Server properties
> http://db.apache.org/derby/docs/dev/adminguide/tadminconfigsettingnetwrokserverproperties.html
> Add this new property
> derby.drda.securityMechanism
> Restricts client connections based on the security mechanism.
> if derby.drda.securityMechanism is set to a valid mechanism, then
> the Network Server accepts only connections which use that
> security mechanism. No other types of connections are accepted.
> if the derby.drda.securityMechanism is not set at all, then the
> Network Server accepts any connection which uses a valid
> security mechanism.
> Syntax:
> derby.drda.securityMechanism=[USER_ONLY_SECURITY|CLEAR_TEXT_PASSWORD_SECURITY|ENCRYPTED_USER_AND_PASSWORD_SECURITY]
> Example:
> derby.drda.securityMechanism=USER_ONLY_SECURITY
> The server running with this property will only accept client connections with USER_ONLY_SECURITY.
> Static or Dynamic:
> This property is static. Server must be restarted for the property to take effect.
> Default value for this property is as though it is not set - in which case
> the server will allow clients with supported security mechanisms to connect
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-1682) Add documentation for
derby.drda.securityMechanism.
Posted by "Jean T. Anderson (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1682?page=comments#action_12432950 ]
Jean T. Anderson commented on DERBY-1682:
-----------------------------------------
Committed patch derby1682_083106.diff to the trunk, revision 440848 (not merged to the 10.2 branch yet).
> Add documentation for derby.drda.securityMechanism.
> ---------------------------------------------------
>
> Key: DERBY-1682
> URL: http://issues.apache.org/jira/browse/DERBY-1682
> Project: Derby
> Issue Type: Task
> Components: Documentation
> Reporter: Sunitha Kambhampati
> Assigned To: Laura Stewart
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby1682_083106.diff, derby1682_adminguide.diff, derby1682_update.diff, radmindrdasecmechanism.html, radmindrdasecmechanism090106.html, radmindrdasecmechanism_083106.html, radmindrdasecmechanism_update.html
>
>
> Under section Setting Network Server properties
> http://db.apache.org/derby/docs/dev/adminguide/tadminconfigsettingnetwrokserverproperties.html
> Add this new property
> derby.drda.securityMechanism
> Restricts client connections based on the security mechanism.
> if derby.drda.securityMechanism is set to a valid mechanism, then
> the Network Server accepts only connections which use that
> security mechanism. No other types of connections are accepted.
> if the derby.drda.securityMechanism is not set at all, then the
> Network Server accepts any connection which uses a valid
> security mechanism.
> Syntax:
> derby.drda.securityMechanism=[USER_ONLY_SECURITY|CLEAR_TEXT_PASSWORD_SECURITY|ENCRYPTED_USER_AND_PASSWORD_SECURITY]
> Example:
> derby.drda.securityMechanism=USER_ONLY_SECURITY
> The server running with this property will only accept client connections with USER_ONLY_SECURITY.
> Static or Dynamic:
> This property is static. Server must be restarted for the property to take effect.
> Default value for this property is as though it is not set - in which case
> the server will allow clients with supported security mechanisms to connect
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-1682) Add documentation for
derby.drda.securityMechanism.
Posted by "Laura Stewart (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1682?page=comments#action_12431950 ]
Laura Stewart commented on DERBY-1682:
--------------------------------------
Hi Kim -
The syntax is really long, and I am forced to scroll my window (in HTML) even though
my window is full screen. I assume that the PDF is not a problem since there are spaces in the syntax
and PDF usually forces a carriage return. But the HTML isn't as good as it could be.
The other properties are very short, but if you look at the Reference Manual under the SQL Statements,
many of those have syntaxes that are on multiple lines. What do you think about forcing a carriage return so
that the HMTL looks better?
> Add documentation for derby.drda.securityMechanism.
> ---------------------------------------------------
>
> Key: DERBY-1682
> URL: http://issues.apache.org/jira/browse/DERBY-1682
> Project: Derby
> Issue Type: Task
> Components: Documentation
> Reporter: Sunitha Kambhampati
> Assigned To: Laura Stewart
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby1682_adminguide.diff, derby1682_update.diff, radmindrdasecmechanism.html, radmindrdasecmechanism_update.html
>
>
> Under section Setting Network Server properties
> http://db.apache.org/derby/docs/dev/adminguide/tadminconfigsettingnetwrokserverproperties.html
> Add this new property
> derby.drda.securityMechanism
> Restricts client connections based on the security mechanism.
> if derby.drda.securityMechanism is set to a valid mechanism, then
> the Network Server accepts only connections which use that
> security mechanism. No other types of connections are accepted.
> if the derby.drda.securityMechanism is not set at all, then the
> Network Server accepts any connection which uses a valid
> security mechanism.
> Syntax:
> derby.drda.securityMechanism=[USER_ONLY_SECURITY|CLEAR_TEXT_PASSWORD_SECURITY|ENCRYPTED_USER_AND_PASSWORD_SECURITY]
> Example:
> derby.drda.securityMechanism=USER_ONLY_SECURITY
> The server running with this property will only accept client connections with USER_ONLY_SECURITY.
> Static or Dynamic:
> This property is static. Server must be restarted for the property to take effect.
> Default value for this property is as though it is not set - in which case
> the server will allow clients with supported security mechanisms to connect
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-1682) Add documentation for
derby.drda.securityMechanism.
Posted by "Laura Stewart (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1682?page=comments#action_12432661 ]
Laura Stewart commented on DERBY-1682:
--------------------------------------
Kim - This update looks good to me. +1 to commit.
> Add documentation for derby.drda.securityMechanism.
> ---------------------------------------------------
>
> Key: DERBY-1682
> URL: http://issues.apache.org/jira/browse/DERBY-1682
> Project: Derby
> Issue Type: Task
> Components: Documentation
> Reporter: Sunitha Kambhampati
> Assigned To: Laura Stewart
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby1682_083106.diff, derby1682_adminguide.diff, derby1682_update.diff, radmindrdasecmechanism.html, radmindrdasecmechanism090106.html, radmindrdasecmechanism_083106.html, radmindrdasecmechanism_update.html
>
>
> Under section Setting Network Server properties
> http://db.apache.org/derby/docs/dev/adminguide/tadminconfigsettingnetwrokserverproperties.html
> Add this new property
> derby.drda.securityMechanism
> Restricts client connections based on the security mechanism.
> if derby.drda.securityMechanism is set to a valid mechanism, then
> the Network Server accepts only connections which use that
> security mechanism. No other types of connections are accepted.
> if the derby.drda.securityMechanism is not set at all, then the
> Network Server accepts any connection which uses a valid
> security mechanism.
> Syntax:
> derby.drda.securityMechanism=[USER_ONLY_SECURITY|CLEAR_TEXT_PASSWORD_SECURITY|ENCRYPTED_USER_AND_PASSWORD_SECURITY]
> Example:
> derby.drda.securityMechanism=USER_ONLY_SECURITY
> The server running with this property will only accept client connections with USER_ONLY_SECURITY.
> Static or Dynamic:
> This property is static. Server must be restarted for the property to take effect.
> Default value for this property is as though it is not set - in which case
> the server will allow clients with supported security mechanisms to connect
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-1682) Add documentation for
derby.drda.securityMechanism.
Posted by "Kim Haase (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1682?page=comments#action_12431337 ]
Kim Haase commented on DERBY-1682:
----------------------------------
Yes, I'll do that.
> Add documentation for derby.drda.securityMechanism.
> ---------------------------------------------------
>
> Key: DERBY-1682
> URL: http://issues.apache.org/jira/browse/DERBY-1682
> Project: Derby
> Issue Type: Task
> Components: Documentation
> Reporter: Sunitha Kambhampati
> Assigned To: Laura Stewart
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby1682_adminguide.diff, radmindrdasecmechanism.html
>
>
> Under section Setting Network Server properties
> http://db.apache.org/derby/docs/dev/adminguide/tadminconfigsettingnetwrokserverproperties.html
> Add this new property
> derby.drda.securityMechanism
> Restricts client connections based on the security mechanism.
> if derby.drda.securityMechanism is set to a valid mechanism, then
> the Network Server accepts only connections which use that
> security mechanism. No other types of connections are accepted.
> if the derby.drda.securityMechanism is not set at all, then the
> Network Server accepts any connection which uses a valid
> security mechanism.
> Syntax:
> derby.drda.securityMechanism=[USER_ONLY_SECURITY|CLEAR_TEXT_PASSWORD_SECURITY|ENCRYPTED_USER_AND_PASSWORD_SECURITY]
> Example:
> derby.drda.securityMechanism=USER_ONLY_SECURITY
> The server running with this property will only accept client connections with USER_ONLY_SECURITY.
> Static or Dynamic:
> This property is static. Server must be restarted for the property to take effect.
> Default value for this property is as though it is not set - in which case
> the server will allow clients with supported security mechanisms to connect
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-1682) Add documentation for
derby.drda.securityMechanism.
Posted by "Sunitha Kambhampati (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1682?page=comments#action_12430096 ]
Sunitha Kambhampati commented on DERBY-1682:
--------------------------------------------
The changes look good. +1 for commit.
Thanks Laura.
> Add documentation for derby.drda.securityMechanism.
> ---------------------------------------------------
>
> Key: DERBY-1682
> URL: http://issues.apache.org/jira/browse/DERBY-1682
> Project: Derby
> Issue Type: Task
> Components: Documentation
> Reporter: Sunitha Kambhampati
> Assigned To: Laura Stewart
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby1682_adminguide.diff, radmindrdasecmechanism.html
>
>
> Under section Setting Network Server properties
> http://db.apache.org/derby/docs/dev/adminguide/tadminconfigsettingnetwrokserverproperties.html
> Add this new property
> derby.drda.securityMechanism
> Restricts client connections based on the security mechanism.
> if derby.drda.securityMechanism is set to a valid mechanism, then
> the Network Server accepts only connections which use that
> security mechanism. No other types of connections are accepted.
> if the derby.drda.securityMechanism is not set at all, then the
> Network Server accepts any connection which uses a valid
> security mechanism.
> Syntax:
> derby.drda.securityMechanism=[USER_ONLY_SECURITY|CLEAR_TEXT_PASSWORD_SECURITY|ENCRYPTED_USER_AND_PASSWORD_SECURITY]
> Example:
> derby.drda.securityMechanism=USER_ONLY_SECURITY
> The server running with this property will only accept client connections with USER_ONLY_SECURITY.
> Static or Dynamic:
> This property is static. Server must be restarted for the property to take effect.
> Default value for this property is as though it is not set - in which case
> the server will allow clients with supported security mechanisms to connect
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-1682) Add documentation for
derby.drda.securityMechanism.
Posted by "Kim Haase (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1682?page=all ]
Kim Haase updated DERBY-1682:
-----------------------------
Attachment: derby1682_update.diff
radmindrdasecmechanism_update.html
Here is a patch that adds the new security mechanism to the syntax. It's an awfully long line of code, but it seems to show up legibly in pdf and monohtml as well as html output. Hope it's satisfactory.
> Add documentation for derby.drda.securityMechanism.
> ---------------------------------------------------
>
> Key: DERBY-1682
> URL: http://issues.apache.org/jira/browse/DERBY-1682
> Project: Derby
> Issue Type: Task
> Components: Documentation
> Reporter: Sunitha Kambhampati
> Assigned To: Laura Stewart
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby1682_adminguide.diff, derby1682_update.diff, radmindrdasecmechanism.html, radmindrdasecmechanism_update.html
>
>
> Under section Setting Network Server properties
> http://db.apache.org/derby/docs/dev/adminguide/tadminconfigsettingnetwrokserverproperties.html
> Add this new property
> derby.drda.securityMechanism
> Restricts client connections based on the security mechanism.
> if derby.drda.securityMechanism is set to a valid mechanism, then
> the Network Server accepts only connections which use that
> security mechanism. No other types of connections are accepted.
> if the derby.drda.securityMechanism is not set at all, then the
> Network Server accepts any connection which uses a valid
> security mechanism.
> Syntax:
> derby.drda.securityMechanism=[USER_ONLY_SECURITY|CLEAR_TEXT_PASSWORD_SECURITY|ENCRYPTED_USER_AND_PASSWORD_SECURITY]
> Example:
> derby.drda.securityMechanism=USER_ONLY_SECURITY
> The server running with this property will only accept client connections with USER_ONLY_SECURITY.
> Static or Dynamic:
> This property is static. Server must be restarted for the property to take effect.
> Default value for this property is as though it is not set - in which case
> the server will allow clients with supported security mechanisms to connect
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-1682) Add documentation for
derby.drda.securityMechanism.
Posted by "Kim Haase (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1682?page=all ]
Kim Haase updated DERBY-1682:
-----------------------------
Attachment: derby1682_083106.diff
radmindrdasecmechanism_083106.html
Thanks, Laura, for the very helpful feedback. I'm attaching derby1682_083106.diff and radmindrdasecmechanism_083106.html, which implement your suggestion. Hope they do the job.
> Add documentation for derby.drda.securityMechanism.
> ---------------------------------------------------
>
> Key: DERBY-1682
> URL: http://issues.apache.org/jira/browse/DERBY-1682
> Project: Derby
> Issue Type: Task
> Components: Documentation
> Reporter: Sunitha Kambhampati
> Assigned To: Laura Stewart
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby1682_083106.diff, derby1682_adminguide.diff, derby1682_update.diff, radmindrdasecmechanism.html, radmindrdasecmechanism_083106.html, radmindrdasecmechanism_update.html
>
>
> Under section Setting Network Server properties
> http://db.apache.org/derby/docs/dev/adminguide/tadminconfigsettingnetwrokserverproperties.html
> Add this new property
> derby.drda.securityMechanism
> Restricts client connections based on the security mechanism.
> if derby.drda.securityMechanism is set to a valid mechanism, then
> the Network Server accepts only connections which use that
> security mechanism. No other types of connections are accepted.
> if the derby.drda.securityMechanism is not set at all, then the
> Network Server accepts any connection which uses a valid
> security mechanism.
> Syntax:
> derby.drda.securityMechanism=[USER_ONLY_SECURITY|CLEAR_TEXT_PASSWORD_SECURITY|ENCRYPTED_USER_AND_PASSWORD_SECURITY]
> Example:
> derby.drda.securityMechanism=USER_ONLY_SECURITY
> The server running with this property will only accept client connections with USER_ONLY_SECURITY.
> Static or Dynamic:
> This property is static. Server must be restarted for the property to take effect.
> Default value for this property is as though it is not set - in which case
> the server will allow clients with supported security mechanisms to connect
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-1682) Add documentation for
derby.drda.securityMechanism.
Posted by "Laura Stewart (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1682?page=all ]
Laura Stewart updated DERBY-1682:
---------------------------------
Derby Info: [Patch Available]
> Add documentation for derby.drda.securityMechanism.
> ---------------------------------------------------
>
> Key: DERBY-1682
> URL: http://issues.apache.org/jira/browse/DERBY-1682
> Project: Derby
> Issue Type: Task
> Components: Documentation
> Reporter: Sunitha Kambhampati
> Assigned To: Laura Stewart
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby1682_adminguide.diff, radmindrdasecmechanism.html
>
>
> Under section Setting Network Server properties
> http://db.apache.org/derby/docs/dev/adminguide/tadminconfigsettingnetwrokserverproperties.html
> Add this new property
> derby.drda.securityMechanism
> Restricts client connections based on the security mechanism.
> if derby.drda.securityMechanism is set to a valid mechanism, then
> the Network Server accepts only connections which use that
> security mechanism. No other types of connections are accepted.
> if the derby.drda.securityMechanism is not set at all, then the
> Network Server accepts any connection which uses a valid
> security mechanism.
> Syntax:
> derby.drda.securityMechanism=[USER_ONLY_SECURITY|CLEAR_TEXT_PASSWORD_SECURITY|ENCRYPTED_USER_AND_PASSWORD_SECURITY]
> Example:
> derby.drda.securityMechanism=USER_ONLY_SECURITY
> The server running with this property will only accept client connections with USER_ONLY_SECURITY.
> Static or Dynamic:
> This property is static. Server must be restarted for the property to take effect.
> Default value for this property is as though it is not set - in which case
> the server will allow clients with supported security mechanisms to connect
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (DERBY-1682) Add documentation for
derby.drda.securityMechanism.
Posted by "Laura Stewart (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1682?page=all ]
Laura Stewart resolved DERBY-1682.
----------------------------------
Fix Version/s: 10.2.1.0
(was: 10.3.0.0)
Resolution: Fixed
The issue has been fixed.
The latest patch that Jean committed needs to be merged into the 10.2 trunk.
> Add documentation for derby.drda.securityMechanism.
> ---------------------------------------------------
>
> Key: DERBY-1682
> URL: http://issues.apache.org/jira/browse/DERBY-1682
> Project: Derby
> Issue Type: Task
> Components: Documentation
> Reporter: Sunitha Kambhampati
> Assigned To: Laura Stewart
> Priority: Minor
> Fix For: 10.2.1.0
>
> Attachments: derby1682_083106.diff, derby1682_adminguide.diff, derby1682_update.diff, radmindrdasecmechanism.html, radmindrdasecmechanism090106.html, radmindrdasecmechanism_083106.html, radmindrdasecmechanism_update.html
>
>
> Under section Setting Network Server properties
> http://db.apache.org/derby/docs/dev/adminguide/tadminconfigsettingnetwrokserverproperties.html
> Add this new property
> derby.drda.securityMechanism
> Restricts client connections based on the security mechanism.
> if derby.drda.securityMechanism is set to a valid mechanism, then
> the Network Server accepts only connections which use that
> security mechanism. No other types of connections are accepted.
> if the derby.drda.securityMechanism is not set at all, then the
> Network Server accepts any connection which uses a valid
> security mechanism.
> Syntax:
> derby.drda.securityMechanism=[USER_ONLY_SECURITY|CLEAR_TEXT_PASSWORD_SECURITY|ENCRYPTED_USER_AND_PASSWORD_SECURITY]
> Example:
> derby.drda.securityMechanism=USER_ONLY_SECURITY
> The server running with this property will only accept client connections with USER_ONLY_SECURITY.
> Static or Dynamic:
> This property is static. Server must be restarted for the property to take effect.
> Default value for this property is as though it is not set - in which case
> the server will allow clients with supported security mechanisms to connect
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-1682) Add documentation for
derby.drda.securityMechanism.
Posted by "Francois Orsini (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1682?page=comments#action_12430333 ]
Francois Orsini commented on DERBY-1682:
----------------------------------------
Hi Kim,
Yes, STRONG_PASSWORD_SUBSTITUTE_SECURITY should be added to the list and as part of the 3 other already listed...
Thanks and good catch.
--francois
> Add documentation for derby.drda.securityMechanism.
> ---------------------------------------------------
>
> Key: DERBY-1682
> URL: http://issues.apache.org/jira/browse/DERBY-1682
> Project: Derby
> Issue Type: Task
> Components: Documentation
> Reporter: Sunitha Kambhampati
> Assigned To: Laura Stewart
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby1682_adminguide.diff, radmindrdasecmechanism.html
>
>
> Under section Setting Network Server properties
> http://db.apache.org/derby/docs/dev/adminguide/tadminconfigsettingnetwrokserverproperties.html
> Add this new property
> derby.drda.securityMechanism
> Restricts client connections based on the security mechanism.
> if derby.drda.securityMechanism is set to a valid mechanism, then
> the Network Server accepts only connections which use that
> security mechanism. No other types of connections are accepted.
> if the derby.drda.securityMechanism is not set at all, then the
> Network Server accepts any connection which uses a valid
> security mechanism.
> Syntax:
> derby.drda.securityMechanism=[USER_ONLY_SECURITY|CLEAR_TEXT_PASSWORD_SECURITY|ENCRYPTED_USER_AND_PASSWORD_SECURITY]
> Example:
> derby.drda.securityMechanism=USER_ONLY_SECURITY
> The server running with this property will only accept client connections with USER_ONLY_SECURITY.
> Static or Dynamic:
> This property is static. Server must be restarted for the property to take effect.
> Default value for this property is as though it is not set - in which case
> the server will allow clients with supported security mechanisms to connect
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-1682) Add documentation for
derby.drda.securityMechanism.
Posted by "Kim Haase (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1682?page=comments#action_12431966 ]
Kim Haase commented on DERBY-1682:
----------------------------------
Thanks for the suggestion, Laura. I was wondering about that. I'm not sure spacing will come out right here, but do you think I should just do the one carriage return to make it legible --
derby.drda.securityMechanism = [ USER_ONLY_SECURITY | CLEAR_TEXT_PASSWORD_SECURITY |
ENCRYPTED_USER_AND_PASSWORD_SECURITY | STRONG_PASSWORD_SUBSTITUTE_SECURITY ]
or something more like this, with one property value per line?
derby.drda.securityMechanism = [
USER_ONLY_SECURITY |
CLEAR_TEXT_PASSWORD_SECURITY |
ENCRYPTED_USER_AND_PASSWORD_SECURITY |
STRONG_PASSWORD_SUBSTITUTE_SECURITY
]
There seem to be examples of both sorts in the adminguide and ref manuals.
You are right that the PDF forces a carriage return.
> Add documentation for derby.drda.securityMechanism.
> ---------------------------------------------------
>
> Key: DERBY-1682
> URL: http://issues.apache.org/jira/browse/DERBY-1682
> Project: Derby
> Issue Type: Task
> Components: Documentation
> Reporter: Sunitha Kambhampati
> Assigned To: Laura Stewart
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby1682_adminguide.diff, derby1682_update.diff, radmindrdasecmechanism.html, radmindrdasecmechanism_update.html
>
>
> Under section Setting Network Server properties
> http://db.apache.org/derby/docs/dev/adminguide/tadminconfigsettingnetwrokserverproperties.html
> Add this new property
> derby.drda.securityMechanism
> Restricts client connections based on the security mechanism.
> if derby.drda.securityMechanism is set to a valid mechanism, then
> the Network Server accepts only connections which use that
> security mechanism. No other types of connections are accepted.
> if the derby.drda.securityMechanism is not set at all, then the
> Network Server accepts any connection which uses a valid
> security mechanism.
> Syntax:
> derby.drda.securityMechanism=[USER_ONLY_SECURITY|CLEAR_TEXT_PASSWORD_SECURITY|ENCRYPTED_USER_AND_PASSWORD_SECURITY]
> Example:
> derby.drda.securityMechanism=USER_ONLY_SECURITY
> The server running with this property will only accept client connections with USER_ONLY_SECURITY.
> Static or Dynamic:
> This property is static. Server must be restarted for the property to take effect.
> Default value for this property is as though it is not set - in which case
> the server will allow clients with supported security mechanisms to connect
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-1682) Add documentation for
derby.drda.securityMechanism.
Posted by "Rick Hillegas (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1682?page=comments#action_12430647 ]
Rick Hillegas commented on DERBY-1682:
--------------------------------------
Ported DERBY-1682 (434218) to 10.2 branch at subversion revision 436974.
> Add documentation for derby.drda.securityMechanism.
> ---------------------------------------------------
>
> Key: DERBY-1682
> URL: http://issues.apache.org/jira/browse/DERBY-1682
> Project: Derby
> Issue Type: Task
> Components: Documentation
> Reporter: Sunitha Kambhampati
> Assigned To: Laura Stewart
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby1682_adminguide.diff, radmindrdasecmechanism.html
>
>
> Under section Setting Network Server properties
> http://db.apache.org/derby/docs/dev/adminguide/tadminconfigsettingnetwrokserverproperties.html
> Add this new property
> derby.drda.securityMechanism
> Restricts client connections based on the security mechanism.
> if derby.drda.securityMechanism is set to a valid mechanism, then
> the Network Server accepts only connections which use that
> security mechanism. No other types of connections are accepted.
> if the derby.drda.securityMechanism is not set at all, then the
> Network Server accepts any connection which uses a valid
> security mechanism.
> Syntax:
> derby.drda.securityMechanism=[USER_ONLY_SECURITY|CLEAR_TEXT_PASSWORD_SECURITY|ENCRYPTED_USER_AND_PASSWORD_SECURITY]
> Example:
> derby.drda.securityMechanism=USER_ONLY_SECURITY
> The server running with this property will only accept client connections with USER_ONLY_SECURITY.
> Static or Dynamic:
> This property is static. Server must be restarted for the property to take effect.
> Default value for this property is as though it is not set - in which case
> the server will allow clients with supported security mechanisms to connect
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-1682) Add documentation for
derby.drda.securityMechanism.
Posted by "Kim Haase (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1682?page=comments#action_12431349 ]
Kim Haase commented on DERBY-1682:
----------------------------------
Sorry, I meant to add that the new files have "_update" in the file names.
> Add documentation for derby.drda.securityMechanism.
> ---------------------------------------------------
>
> Key: DERBY-1682
> URL: http://issues.apache.org/jira/browse/DERBY-1682
> Project: Derby
> Issue Type: Task
> Components: Documentation
> Reporter: Sunitha Kambhampati
> Assigned To: Laura Stewart
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby1682_adminguide.diff, derby1682_update.diff, radmindrdasecmechanism.html, radmindrdasecmechanism_update.html
>
>
> Under section Setting Network Server properties
> http://db.apache.org/derby/docs/dev/adminguide/tadminconfigsettingnetwrokserverproperties.html
> Add this new property
> derby.drda.securityMechanism
> Restricts client connections based on the security mechanism.
> if derby.drda.securityMechanism is set to a valid mechanism, then
> the Network Server accepts only connections which use that
> security mechanism. No other types of connections are accepted.
> if the derby.drda.securityMechanism is not set at all, then the
> Network Server accepts any connection which uses a valid
> security mechanism.
> Syntax:
> derby.drda.securityMechanism=[USER_ONLY_SECURITY|CLEAR_TEXT_PASSWORD_SECURITY|ENCRYPTED_USER_AND_PASSWORD_SECURITY]
> Example:
> derby.drda.securityMechanism=USER_ONLY_SECURITY
> The server running with this property will only accept client connections with USER_ONLY_SECURITY.
> Static or Dynamic:
> This property is static. Server must be restarted for the property to take effect.
> Default value for this property is as though it is not set - in which case
> the server will allow clients with supported security mechanisms to connect
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-1682) Add documentation for
derby.drda.securityMechanism.
Posted by "Mamta A. Satoor (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1682?page=comments#action_12430176 ]
Mamta A. Satoor commented on DERBY-1682:
----------------------------------------
I did some buddy testing for DERBY-928 which is the code changes counterpart of this documentation jira entry and just wanted to send my +1 for the doc changes.
> Add documentation for derby.drda.securityMechanism.
> ---------------------------------------------------
>
> Key: DERBY-1682
> URL: http://issues.apache.org/jira/browse/DERBY-1682
> Project: Derby
> Issue Type: Task
> Components: Documentation
> Reporter: Sunitha Kambhampati
> Assigned To: Laura Stewart
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby1682_adminguide.diff, radmindrdasecmechanism.html
>
>
> Under section Setting Network Server properties
> http://db.apache.org/derby/docs/dev/adminguide/tadminconfigsettingnetwrokserverproperties.html
> Add this new property
> derby.drda.securityMechanism
> Restricts client connections based on the security mechanism.
> if derby.drda.securityMechanism is set to a valid mechanism, then
> the Network Server accepts only connections which use that
> security mechanism. No other types of connections are accepted.
> if the derby.drda.securityMechanism is not set at all, then the
> Network Server accepts any connection which uses a valid
> security mechanism.
> Syntax:
> derby.drda.securityMechanism=[USER_ONLY_SECURITY|CLEAR_TEXT_PASSWORD_SECURITY|ENCRYPTED_USER_AND_PASSWORD_SECURITY]
> Example:
> derby.drda.securityMechanism=USER_ONLY_SECURITY
> The server running with this property will only accept client connections with USER_ONLY_SECURITY.
> Static or Dynamic:
> This property is static. Server must be restarted for the property to take effect.
> Default value for this property is as though it is not set - in which case
> the server will allow clients with supported security mechanisms to connect
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (DERBY-1682) Add documentation for
derby.drda.securityMechanism.
Posted by "Laura Stewart (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1682?page=all ]
Laura Stewart reassigned DERBY-1682:
------------------------------------
Assignee: Laura Stewart
> Add documentation for derby.drda.securityMechanism.
> ---------------------------------------------------
>
> Key: DERBY-1682
> URL: http://issues.apache.org/jira/browse/DERBY-1682
> Project: Derby
> Issue Type: Task
> Components: Documentation
> Reporter: Sunitha Kambhampati
> Assigned To: Laura Stewart
> Priority: Minor
> Fix For: 10.2.0.0
>
>
> Under section Setting Network Server properties
> http://db.apache.org/derby/docs/dev/adminguide/tadminconfigsettingnetwrokserverproperties.html
> Add this new property
> derby.drda.securityMechanism
> Restricts client connections based on the security mechanism.
> if derby.drda.securityMechanism is set to a valid mechanism, then
> the Network Server accepts only connections which use that
> security mechanism. No other types of connections are accepted.
> if the derby.drda.securityMechanism is not set at all, then the
> Network Server accepts any connection which uses a valid
> security mechanism.
> Syntax:
> derby.drda.securityMechanism=[USER_ONLY_SECURITY|CLEAR_TEXT_PASSWORD_SECURITY|ENCRYPTED_USER_AND_PASSWORD_SECURITY]
> Example:
> derby.drda.securityMechanism=USER_ONLY_SECURITY
> The server running with this property will only accept client connections with USER_ONLY_SECURITY.
> Static or Dynamic:
> This property is static. Server must be restarted for the property to take effect.
> Default value for this property is as though it is not set - in which case
> the server will allow clients with supported security mechanisms to connect
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-1682) Add documentation for
derby.drda.securityMechanism.
Posted by "Laura Stewart (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1682?page=comments#action_12431973 ]
Laura Stewart commented on DERBY-1682:
--------------------------------------
Yes, unfortunately there isn't as much consistency as there should be in the docs :-)
I like the second approach, with one property value per line. It will also ensure that the PDF looks the same as
the HTML. If you use the first approach it is possible that the HTML and PDF won't appear the same.
Thanks for fixing this !
> Add documentation for derby.drda.securityMechanism.
> ---------------------------------------------------
>
> Key: DERBY-1682
> URL: http://issues.apache.org/jira/browse/DERBY-1682
> Project: Derby
> Issue Type: Task
> Components: Documentation
> Reporter: Sunitha Kambhampati
> Assigned To: Laura Stewart
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby1682_adminguide.diff, derby1682_update.diff, radmindrdasecmechanism.html, radmindrdasecmechanism_update.html
>
>
> Under section Setting Network Server properties
> http://db.apache.org/derby/docs/dev/adminguide/tadminconfigsettingnetwrokserverproperties.html
> Add this new property
> derby.drda.securityMechanism
> Restricts client connections based on the security mechanism.
> if derby.drda.securityMechanism is set to a valid mechanism, then
> the Network Server accepts only connections which use that
> security mechanism. No other types of connections are accepted.
> if the derby.drda.securityMechanism is not set at all, then the
> Network Server accepts any connection which uses a valid
> security mechanism.
> Syntax:
> derby.drda.securityMechanism=[USER_ONLY_SECURITY|CLEAR_TEXT_PASSWORD_SECURITY|ENCRYPTED_USER_AND_PASSWORD_SECURITY]
> Example:
> derby.drda.securityMechanism=USER_ONLY_SECURITY
> The server running with this property will only accept client connections with USER_ONLY_SECURITY.
> Static or Dynamic:
> This property is static. Server must be restarted for the property to take effect.
> Default value for this property is as though it is not set - in which case
> the server will allow clients with supported security mechanisms to connect
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-1682) Add documentation for
derby.drda.securityMechanism.
Posted by "Jean T. Anderson (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1682?page=all ]
Jean T. Anderson updated DERBY-1682:
------------------------------------
Derby Info: (was: [Patch Available])
> Add documentation for derby.drda.securityMechanism.
> ---------------------------------------------------
>
> Key: DERBY-1682
> URL: http://issues.apache.org/jira/browse/DERBY-1682
> Project: Derby
> Issue Type: Task
> Components: Documentation
> Reporter: Sunitha Kambhampati
> Assigned To: Laura Stewart
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby1682_083106.diff, derby1682_adminguide.diff, derby1682_update.diff, radmindrdasecmechanism.html, radmindrdasecmechanism090106.html, radmindrdasecmechanism_083106.html, radmindrdasecmechanism_update.html
>
>
> Under section Setting Network Server properties
> http://db.apache.org/derby/docs/dev/adminguide/tadminconfigsettingnetwrokserverproperties.html
> Add this new property
> derby.drda.securityMechanism
> Restricts client connections based on the security mechanism.
> if derby.drda.securityMechanism is set to a valid mechanism, then
> the Network Server accepts only connections which use that
> security mechanism. No other types of connections are accepted.
> if the derby.drda.securityMechanism is not set at all, then the
> Network Server accepts any connection which uses a valid
> security mechanism.
> Syntax:
> derby.drda.securityMechanism=[USER_ONLY_SECURITY|CLEAR_TEXT_PASSWORD_SECURITY|ENCRYPTED_USER_AND_PASSWORD_SECURITY]
> Example:
> derby.drda.securityMechanism=USER_ONLY_SECURITY
> The server running with this property will only accept client connections with USER_ONLY_SECURITY.
> Static or Dynamic:
> This property is static. Server must be restarted for the property to take effect.
> Default value for this property is as though it is not set - in which case
> the server will allow clients with supported security mechanisms to connect
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-1682) Add documentation for
derby.drda.securityMechanism.
Posted by "Laura Stewart (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1682?page=comments#action_12431278 ]
Laura Stewart commented on DERBY-1682:
--------------------------------------
Kim - Are you going to update the topic to add the security mechanism info?
> Add documentation for derby.drda.securityMechanism.
> ---------------------------------------------------
>
> Key: DERBY-1682
> URL: http://issues.apache.org/jira/browse/DERBY-1682
> Project: Derby
> Issue Type: Task
> Components: Documentation
> Reporter: Sunitha Kambhampati
> Assigned To: Laura Stewart
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby1682_adminguide.diff, radmindrdasecmechanism.html
>
>
> Under section Setting Network Server properties
> http://db.apache.org/derby/docs/dev/adminguide/tadminconfigsettingnetwrokserverproperties.html
> Add this new property
> derby.drda.securityMechanism
> Restricts client connections based on the security mechanism.
> if derby.drda.securityMechanism is set to a valid mechanism, then
> the Network Server accepts only connections which use that
> security mechanism. No other types of connections are accepted.
> if the derby.drda.securityMechanism is not set at all, then the
> Network Server accepts any connection which uses a valid
> security mechanism.
> Syntax:
> derby.drda.securityMechanism=[USER_ONLY_SECURITY|CLEAR_TEXT_PASSWORD_SECURITY|ENCRYPTED_USER_AND_PASSWORD_SECURITY]
> Example:
> derby.drda.securityMechanism=USER_ONLY_SECURITY
> The server running with this property will only accept client connections with USER_ONLY_SECURITY.
> Static or Dynamic:
> This property is static. Server must be restarted for the property to take effect.
> Default value for this property is as though it is not set - in which case
> the server will allow clients with supported security mechanisms to connect
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira