db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kim Haase <Camilla.Ha...@Sun.COM>
Subject Re: [jira] Updated: (DERBY-1682) Add documentation for derby.drda.securityMechanism.
Date Fri, 01 Sep 2006 18:32:07 GMT
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) <derby-dev@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
>>
>>
>>
> 
> 
> 


Mime
View raw message