Please let me know what approach you've used...

On Fri, Mar 27, 2009 at 11:35 PM, mdipierro <mdipie...@cs.depaul.edu> wrote:

>
> There is no standard mechanism for this. One would have to be created.
>
> On Mar 27, 9:48 am, Oliver Heyme <oli...@googlemail.com> wrote:
> > If that's the case I will probably create my own auto mechanism!
> > It would have been pretty cool to just use the "Standard".
> >
> > Too sad!
> >
> > On Fri, Mar 27, 2009 at 3:41 PM, Tito Garrido <titogarr...@gmail.com>
> wrote:
> > > I'm interested on this answer too... :)
> >
> > > I don't know if it's a good approach... but you could auth using a
> function
> > > that receives the username and password and the returns a "token" that
> > > expires in a certain time, requiring a new authentication.
> >
> > > Any other ideas?
> >
> > > Tito Garrido
> >
> > > On Tue, Mar 24, 2009 at 4:59 AM, oli...@googlemail.com
> > > <oli...@googlemail.com> wrote:
> >
> > >> Hi,
> >
> > >> I started using web2py as a data backend and therefore most of the
> > >> function are exported via xml-rpc and only a few views exists for a
> > >> minimal web-interface.
> >
> > >> Now I have the following problem. I have added the "Auth" service and
> > >> it works really fine when I work with the web-interfaces (views).
> >
> > >> But how do I authenticate a user via xml-rpc?
> >
> > >> Thanks in advance,
> > >> Oli
> >
> > > --
> > > Linux User #387870
> > > .........____
> > > .... _/_õ|__|
> > > ..º[ .-.___.-._| . . . .
> > > .__( o)__( o).:_______
> >
>


-- 
Linux User #387870
.........____
.... _/_õ|__|
..º[ .-.___.-._| . . . .
.__( o)__( o).:_______

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"web2py Web Framework" group.
To post to this group, send email to web2py@googlegroups.com
To unsubscribe from this group, send email to 
web2py+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/web2py?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to