Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Received-SPF: pass (athena.apache.org: domain of nux@li.nux.ro designates
 31.193.175.196 as permitted sender)
Date: Wed, 11 Mar 2015 13:39:53 +0000 (GMT)
From: Nux! <nux@li.nux.ro>
To: dev@cloudstack.apache.org
Message-ID: <795506513.5253.1426081193106.JavaMail.zimbra@li.nux.ro>
In-Reply-To: <55004005.9040103@widodh.nl>
References: <54FFF820.90708@shapeblue.com>
 <991920344.5166.1426079394252.JavaMail.zimbra@li.nux.ro>
 <55004005.9040103@widodh.nl>
Subject: Re: [DISCUSS] VR Password server improvement and expiring
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Thread-Topic: VR Password server improvement and expiring
Thread-Index: Mh2ni+nhTfhg64Qu7MNAAAI7/cS73w==

Hi Wido,


>> If a guest has confirmed the password was retrieved delete it
>> straight away. I am not sure this is what you asked. :)
>> 
> 
> How would the guest confirm? Merely retrieving it doesn't guarantee
> that the client was able to set it.
> 
> I'd say keep if for 15 minutes, so that the guest can try a couple of
> times before we expire the password.

Nothing against keeping the password around for a few more minutes or hours.

Looking at this password script[1] for example, it looks like the guest can confirm that password was successfully retrieved and set like this:

wget -t 3 -T 20 -O - --header "DomU_Request: saved_password" $PASSWORD_SERVER_IP:8080


[1] - https://raw.githubusercontent.com/shankerbalan/cloudstack-scripts/master/archlinux/cloudstack-set-guest-password