Re: GWT security

I don't think that security is just about encrypting RPC calls. And as
cokol said if encrypted RPC stream is the only concern it should go
through HTTPs. The purpose of acris-security is to integrate server
side security with GWT client, propagating authentication and
authorization "things" (like allowing a user to see or manipulate
certain kind of data),...

And yes, it is fancy ;) but not only RPC call ;)

On 11. Aug, 14:04 h., Luis Daniel Mesa Velasquez
<luisdanielm...@gmail.com> wrote:
> I don't see anything about the encryption used in the RPC call to the
> userservice... so it's just a fancy 3rd party RPC call, no security
> there...
>
> On Aug 10, 3:20 am, Peter Simun <si...@seges.sk> wrote:
>
> > Hi all,
>
> > I just wanted to share with you the article about security in GWT
> > application.http://java.dzone.com/articles/securing-gwt-client-acris
>
> > Serious security implementation is something that was missing almost
> > to each GWT developer. I saw many topics here in the forum about the
> > security, so maybe it will helps you to implement security in a
> > correct way.
>
> > Peter

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