Thanks for but that is more on implementing authentication, I am looking for authentication and authorization for REST API, I understand single key would be better idea, but do we have any real example or guide line?
On Sat, Mar 12, 2011 at 1:36 AM, shawn wilson <[email protected]> wrote: > > > On Fri, Mar 11, 2011 at 3:00 PM, Devin Austin <[email protected]>wrote: > >> >> >> On Fri, Mar 11, 2011 at 12:48 PM, linuxsupport <[email protected]>wrote: >> >>> Hi Everyone, >>> >>> What is the best practice for implementation authentication and >>> authorization when building a REST API application using catalyst? >>> How should authentication be implementation? >>> >>> Any guide or example would be very helpful. >>> Dev site: http://dev.catalyst.perl.org/ >>> >>> >> Probably an API key system. It's much easier to maintain a single key >> instead of having to pass a username/password each time you make a request >> or what not. >> >> >> >> i found this useful: > http://www.gossamer-threads.com/lists/catalyst/users/28136 > ... though i haven't implemented anything yet. > > _______________________________________________ > List: [email protected] > Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst > Searchable archive: > http://www.mail-archive.com/[email protected]/ > Dev site: http://dev.catalyst.perl.org/ > >
_______________________________________________ List: [email protected] Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/[email protected]/ Dev site: http://dev.catalyst.perl.org/
