> Don't authenticators work as plugins in cloudstack with plain text
authenticator as default? I think we should leave it for the customer to
decide whether he wants to disable or keep the authenticator
Couldn't agree more with this! Going through each authenticator until a
successful result is fo
al Message-
From: Ian Duffy [mailto:i...@ianduffy.ie]
Sent: Friday, September 13, 2013 2:52 AM
To: CloudStack Dev
Subject: Re: plain text authenticator
> Don't authenticators work as plugins in cloudstack with plain text
authenticator as default? I think we should leave it for the customer to
Are all authentication plugins loaded by default and working in an
authentication chain?
Otherwise why should we keep the hash type in DB?
> -Original Message-
> From: Darren Shepherd [mailto:darren.s.sheph...@gmail.com]
> Sent: Thursday, September 12, 2013 9:56 AM
> To: dev@cloudstack.ap
Don't authenticators work as plugins in cloudstack with plain text
authenticator as default? I think we should leave it for the customer to
decide whether he wants to disable or keep the authenticator. If he
decided to get rid of it, then steps mentioned by Vijay should be executed
(update existing
Good catch Darren - the plain text authenticator was only preserved to
support older clients that still hashed their passwords to md5. Indeed,
storing the hash type would be required so only the appropriate
authenticator would be invoked. However, we need to ensure that upgrades
are correctly handl
