db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Closed: (DERBY-4004) Remove required RDBNAM from ACCSEC. Use SECCHK RDBNAM if none is provided on ACCSEC
Date Wed, 14 Jan 2009 21:32:59 GMT

     [ https://issues.apache.org/jira/browse/DERBY-4004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kathey Marsden closed DERBY-4004.
---------------------------------

       Resolution: Fixed
    Fix Version/s: 10.5.0.0

>  Remove required RDBNAM from ACCSEC. Use SECCHK RDBNAM if none is provided on ACCSEC
> ------------------------------------------------------------------------------------
>
>                 Key: DERBY-4004
>                 URL: https://issues.apache.org/jira/browse/DERBY-4004
>             Project: Derby
>          Issue Type: Sub-task
>          Components: Network Client, Network Server
>    Affects Versions: 10.5.0.0
>            Reporter: Kathey Marsden
>            Assignee: Kathey Marsden
>            Priority: Minor
>             Fix For: 10.5.0.0
>
>         Attachments: derby-4004-fix_new_protcoltest.diff, derby-4004_diff.txt
>
>
> Currently Derby requires RDBNAM on ACCSEC. The DDM spec lists it as optional. For DERBY-728,
in order to negotiate the encoding, EXCSAT and ACCSEC will need to remain EBCDIC, so we want
the RDBNAM to be optional.  We can use the RDBNAM sent in SECCHK instead.
> Once this is done. Client can be changed to only send RDBNAM on ACCSEC if an EBCDIC conversion
is possible.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message