deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ronelle Landy (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DTACLOUD-49) The rhevm deltcloud-core client has problems handling long usernames
Date Mon, 19 Mar 2012 22:35:42 GMT

    [ https://issues.apache.org/jira/browse/DTACLOUD-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13232970#comment-13232970
] 

Ronelle Landy commented on DTACLOUD-49:
---------------------------------------

Tried to verify this fix using the rhevm servers available for QE testing:

 - Rhevm server  is connected to a ipa server for auth
 - When trying to create a long (60+ characters) user name to test this JIRA, an error was
returned:

 ipa: ERROR: invalid 'login': can be at most 32 characters

Is there a rhevm server that accepts such a long user name? 
                
> The rhevm deltcloud-core client has problems handling long usernames
> --------------------------------------------------------------------
>
>                 Key: DTACLOUD-49
>                 URL: https://issues.apache.org/jira/browse/DTACLOUD-49
>             Project: DeltaCloud
>          Issue Type: Bug
>          Components: Server
>         Environment: Linux Fedora 14 x86_64
>            Reporter: Francesco Vollero
>            Assignee: Michal Fojtik
>         Attachments: 0001-Fix-rhevm-username-long.patch
>
>
> The rhevm deltcloud-core client has problems handling long usernames. Below the first
two examples work.
> But the last example does not. The examples are prints of the headers in clusters method
of rhevm_client.rb after the merge.
> I think the problem is in the auth_header method in rhevm_client.rb. The method calls
Base64.encode64 to encode the username and password. The docs for encode64 says it encodes
lines of 60 characters in length and then adds a LF between each line. It appears that the
LF is causing a problem, but I'm not certain.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message