cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chip Childers <chip.child...@sungard.com>
Subject [ACS41] New API compatibility breakage - blocking release (WAS: createUser in 402 expects password to be MD5 hashed while in 410 plaintext is expected)
Date Wed, 15 May 2013 14:43:12 GMT
I just opened CLOUDSTACK-2516 on this topic.

This is yet another release blocking issue.  Anyone want to take it up?

-chip

On Wed, May 15, 2013 at 04:22:14PM +0200, Ove Ewerlid wrote:
> NB; The 402/410 deployments are on RHES64(OEL64) via RPMs built from
> latest git repos.
> /Ove
> 
> On 05/15/2013 03:02 PM, Ove Ewerlid wrote:
> >Hi!
> >
> >When testing a deploy script, that works as expected with 4.0.2, on 4.1
> >I noticed that there was a need to pass plaintext passwords to
> >createUser, rather then the documented MD5 hash. When passing MD5 hash,
> >the password gets double MD5:hashed in 41.
> >
> >There is new code in 4.1 that encodes password using the authenticator
> >plugins (encode method);
> >
> >cloudstack.4.1/server/src/com/cloud/user/AccountManagerImpl.java
> >
> >        ...
> >        String encodedPassword = null;
> >         for (UserAuthenticator  authenticator : _userAuthenticators) {
> >             encodedPassword = authenticator.encode(password);
> >             if (encodedPassword != null) {
> >                 break;
> >             }
> >         }
> >        ...
> >
> >The 41 API docs still notes that an MD5 hash shall be passed in.
> >What am I missing here?
> >
> >/Ove
> >
> >
> 
> 
> -- 
> Ove Everlid
> System Administrator / Architect / SDN & Linux hacker
> Mobile: +46706662363
> Office: +4618656913 (note EMEA Time Zone)
> 

Mime
View raw message