Hi Schley,

The tutorial you mentionned hasn't been updated yet to take into account the
new security API introduced in Restlet 2.0.

Instead of using a Guard, in most case you will use an Authenticator.
Verifier and Enroler has used by ChallengeAuthenticator to check the
credentials and assign roles for an authenticated user.

I've just checked in some simplification to this security API in SVN trunk
and updated the developers' page on the wiki:

"Security API refactoring" 
http://wiki.restlet.org/developers/172-restlet/212-restlet.html

Best regards,
Jerome Louvel
--
Restlet ~ Founder and Lead developer ~ http://www.restlet.org
Noelios Technologies ~ Co-founder ~ http://www.noelios.com




-----Message d'origine-----
De : Schley Andrew Kutz [mailto:sak...@gmail.com] 
Envoyé : vendredi 11 septembre 2009 06:36
À : discuss@restlet.tigris.org
Objet : Questions about Security Model

I was hoping someone could provide me a little more insight into the
workings of the Restlet security model. I'm currently using M4 and have
created my own Authenticator filter that uses JAAS to do authentication. I
notice that there is also a class called Verifier (which JaasVerifier
appears to be a sub-class of), as well as Enrollers, Subjects, Principals,
etc. However, the flow chart at
http://www.restlet.org/documentation/2.0/tutorial
  (see attached image) explains how Filters are used (and I deduced how to
use them from the guard example -- very nice routing mechanism
-- similar to how IIS handles requests -- I like how it isolates logical
steps -- authenticate, authorize, process, post, etc.), but it makes no
mention of Verifiers or the other classes in the security namespace. I would
love it if I could get a crash course in how to properly handle security
within the Restlet API. Thanks!

------------------------------------------------------
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=23935
15

------------------------------------------------------
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2402912

Reply via email to