Re: REST authentication

Thanks to all. I am thinking about using SSO CAS Authentication too. Did you have an example on how to implement it ? Ray Envoyé depuis iCloud Le 6 oct. 2014 à 02:54, Pascal Robert a écrit : It’s all on wocommunity.org and slideshare.net.        > Hi List,        >        > The answer abou

Re: REST authentication

It’s all on wocommunity.org and slideshare.net. > Hi List, > > The answer about REST auth interests me too. > > Can I download WOWODC 2012 on iTune? > > Thanks. > > Envoyé de mon iPad > > Le 4 oct. 2014 à 21:57, Pascal Robert a écrit : > >> Check my presentations from WOWODC 2012. >> >> En

Re: REST authentication

On 06/10/2014, at 8:45 AM, John Huss wrote: > REST basically just means HTTP, so the answer is to use HTTP auth, most > likely BASIC auth. This can be done two ways: > > 1) If your apps are fronted by Apache (which they probably are), then you can > use Apache's bult-in authorization functio

Re: REST authentication

REST basically just means HTTP, so the answer is to use HTTP auth, most likely BASIC auth. This can be done two ways: 1) If your apps are fronted by Apache (which they probably are), then you can use Apache's bult-in authorization functionality, the simplist form of which is just to declare users

Re: REST authentication

Hi List, The answer about REST auth interests me too. Can I download WOWODC 2012 on iTune? Thanks. Envoyé de mon iPad > Le 4 oct. 2014 à 21:57, Pascal Robert a écrit : > > Check my presentations from WOWODC 2012. > > Envoyé de mon iPhone > >> Le 2014-10-04 à 10:02, Gabor Raz a écrit : >>

Re: REST authentication

Check my presentations from WOWODC 2012. Envoyé de mon iPhone > Le 2014-10-04 à 10:02, Gabor Raz a écrit : > > Hi Guys, > > I normally make my own projects with Node.js. Most of them with the MEAN.IO > framework. But I also came in touch with WebObjects / Project WOnder during > my training

Re: REST Authentication

Actually, the authentication part (and "which approach" discussion/decision with stake-holder) has not been implemented yet. But it is in the TODO pipeline, and not at the top of the TODO list yet. On May 5, 2010, at 5:28 PM, Johnny Miller wrote: > Hi Kieran, > > I was searching my email on th

Re: REST Authentication

Hi Kieran, I was searching my email on this topic and I found this thread. Would you be willing to share your solution that you ended up using for wiring the Rest server to your Cappuccino app? Thanks, Johnny On Mar 19, 2010, at 3:28 PM, Kieran Kelleher wrote: > Actually, I like API keys m

Re: REST Authentication

On 19. Mar, 2010, at 18:28 , Kieran Kelleher wrote: > Now what about the case where API keys are inconvenient for the end client > user. For example, I have a Gianduia Cappuccino app where the user goes to a > site, logs in and works away in his Cappuccino app with occasional REST > requests to

Re: REST Authentication

Actually, I like API keys myself. Simple and easy. Now API keys are ideal for cases where the user wants to change her password for her account, but her API key still stays the same and continues working for whatever client app is using it ... actually Merchant Services sites work like this

Re: REST Authentication

If you have access to OpenBase 11, you could try their XML/JSON server, . On 2010-03-19, at 10:44 AM, Kieran Kelleher wrote: > First, Wonder's ERRest.framework rocks! Thank you again Mike Schrag! and > that is not my first time sayi

Re: REST Authentication

i'm a fan of API keys, personally ... most "web 2.0" sites use them and it's pretty straightforward to hook up. ms On Mar 19, 2010, at 10:44 AM, Kieran Kelleher wrote: > First, Wonder's ERRest.framework rocks! Thank you again Mike Schrag! and > that is not my first time saying that in the

Re: REST Authentication

I agree that it's a mess. I guess you could even use HTTP Digest and HTTP Basic Auth for authentification. Bit.ly use a username and API key system, but like CampaignMonitor, it's over HTTP so if someone sniff your trafic, you're toast. It look like API keys are the way to go for public-but