deltacloud framework and credentials

[Michael Neale]

Hey - Ivan pointed out to me that the Framework is storing the
credentials - I can assume that this is in the session store for rails
for it- I assume this isn't really the intent, and that in practice
deltacloud should either only keep sessions in memory, or not at all,
and just challenge each request?

[Ivan Meredith]

Actaully... I just had a thought. It might be my browser storing and using
the auth header. I didnt think about that until now. Which would explain why
restarting rails didn't help.

2009/10/28 Michael Neale
> Hey - Ivan pointed out to me that the Framework is storing the
> credentials - I can assume that this is in the session store for rails
> for it- I assume this isn't really the intent, and that in practice
> deltacloud should either only keep sessions in memory, or not at all,
> and just challenge each request?
>
> --
> Michael D Neale
> home: www.michaelneale.net
> blog: michaelneale.blogspot.com
> _______________________________________________
> deltacloud-devel mailing list
> [e-mail]
> https://fedorahosted.org/mailman/listinfo/deltacloud-devel

[Michael Neale]

Good point - well I would expect that is it, no need for deltacloud
itself to have any state really?

On Wed, Oct 28, 2009 at 2:05 PM, Ivan Meredith  wrote:
> Actaully... I just had a thought. It might be my browser storing and using
> the auth header. I didnt think about that until now. Which would explain why
> restarting rails didn't help.
>
> 2009/10/28 Michael Neale
> > Hey - Ivan pointed out to me that the Framework is storing the
> > credentials - I can assume that this is in the session store for rails
> > for it- I assume this isn't really the intent, and that in practice
> > deltacloud should either only keep sessions in memory, or not at all,
> > and just challenge each request?
> >
> > --
> > Michael D Neale
> > home: www.michaelneale.net
> > blog: michaelneale.blogspot.com
> > _______________________________________________
> > deltacloud-devel mailing list
> > [e-mail]
> > https://fedorahosted.org/mailman/listinfo/deltacloud-devel

[Hugh O. Brock]

On Wed, Oct 28, 2009 at 02:18:35PM +1100, Michael Neale wrote:
> Good point - well I would expect that is it, no need for deltacloud
> itself to have any state really?

Deltacloud framework explicitly has no state by design. We toyed with
caching credentials to keep connections open, but it proved to be
tedious so we went with a pure stateless model.

FWIW the Deltacloud Portal will store several bits of data including
credentials, cloud pools, and so on, and will expose an API similar to
the framework.

--Hugh
> On Wed, Oct 28, 2009 at 2:05 PM, Ivan Meredith  wrote:
> > Actaully... I just had a thought. It might be my browser storing and using
> > the auth header. I didnt think about that until now. Which would explain why
> > restarting rails didn't help.
> >
> > 2009/10/28 Michael Neale
> > > Hey - Ivan pointed out to me that the Framework is storing the
> > > credentials - I can assume that this is in the session store for rails
> > > for it- I assume this isn't really the intent, and that in practice
> > > deltacloud should either only keep sessions in memory, or not at all,
> > > and just challenge each request?
> > >
> > > --
> > > Michael D Neale
> > > home: www.michaelneale.net
> > > blog: michaelneale.blogspot.com
> > > _______________________________________________
> > > deltacloud-devel mailing list
> > > [e-mail]
> > > https://fedorahosted.org/mailman/listinfo/deltacloud-devel
>
> -- 
> Michael D Neale
> home: www.michaelneale.net
> blog: michaelneale.blogspot.com
> _______________________________________________
> deltacloud-devel mailing list
> [e-mail]
> https://fedorahosted.org/mailman/listinfo/deltacloud-devel

[Bob McWhirter]

Yah, the framework should be 100% stateless.  It has no DB, and  
doesn't use the session.  If there's a cookie being set, we should  
remove that.

The creds go over HTTP Auth, which the browser indeed should cache for  
you and send with all relevant requests.

The client gem does cache the creds, so it can emulate the browser- 
caching of them.

-Bob

On Oct 27, 2009, at 11:18 PM, Michael Neale wrote:
> Good point - well I would expect that is it, no need for deltacloud
> itself to have any state really?
>
> On Wed, Oct 28, 2009 at 2:05 PM, Ivan Meredith   
> wrote:
> > Actaully... I just had a thought. It might be my browser storing  
> > and using
> > the auth header. I didnt think about that until now. Which would  
> > explain why
> > restarting rails didn't help.
> >
> > 2009/10/28 Michael Neale
> > > Hey - Ivan pointed out to me that the Framework is storing the
> > > credentials - I can assume that this is in the session store for  
> > > rails
> > > for it- I assume this isn't really the intent, and that in practice
> > > deltacloud should either only keep sessions in memory, or not at  
> > > all,
> > > and just challenge each request?
> > >
> > > --
> > > Michael D Neale
> > > home: www.michaelneale.net
> > > blog: michaelneale.blogspot.com
> > > _______________________________________________
> > > deltacloud-devel mailing list
> > > [e-mail]
> > > https://fedorahosted.org/mailman/listinfo/deltacloud-devel
>
> -- 
> Michael D Neale
> home: www.michaelneale.net
> blog: michaelneale.blogspot.com
> _______________________________________________
> deltacloud-devel mailing list
> [e-mail]
> https://fedorahosted.org/mailman/listinfo/deltacloud-devel