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

Joerg Schaible resolved VFS-466.
--------------------------------

    Resolution: Fixed

commit -m "Open UserAuthenticationData for arbitrary value types (VFS-466). 
Change requires new getter and setter of the data, deprecate old methods." 
    Sending        
core/src/main/java/org/apache/commons/vfs2/UserAuthenticationData.java
    Sending        
core/src/main/java/org/apache/commons/vfs2/util/UserAuthenticatorUtils.java
    Adding         
core/src/test/java/org/apache/commons/vfs2/UserAuthenticationDataTestCase.java
    Transmitting file data ...
    Committed revision 1450670.
                
> UserAuthenticationData is too limited
> -------------------------------------
>
>                 Key: VFS-466
>                 URL: https://issues.apache.org/jira/browse/VFS-466
>             Project: Commons VFS
>          Issue Type: Improvement
>    Affects Versions: 2.0
>            Reporter: Joerg Schaible
>            Assignee: Joerg Schaible
>             Fix For: 2.1
>
>         Attachments: UserAuthenticationData.patch
>
>
> The UserAuthenticationData should be used as vehicle to transport 
> authentication data to the individual providers. While it is open for new 
> authentication data types, it limits the values of the data to be a character 
> array. Therefore it does not fit for authentication with private keys or 
> certificates like it is possible with e.g. SFTP or FTPS.
> For a proper support of the latter authentication types, we have to support 
> arbitrary value types in the UserAuthenticationData. To add this 
> functionality without breaking binary compatibility, we have to make a 
> compromise by adding new getter/setter methods to the  class that will 
> replace the old (now deprecated ones), because the getter will now return 
> other types than char[].
> This patch is used as base for VFS-283 and for support of client certificates 
> with FTPS (no JIRA issue yet).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to