Hi,
I have a similar requirement. Did anybody try this out? If so, can you
please share some sample code. ?
On Tuesday, 6 November 2012 20:30:59 UTC+5:30, Joseph Lust wrote:
>
> Like Ümit said, you can pass the authorizations provided by your Spring
> Security UserDetailsService to the frontend via an RPC or similar. Then you
> can decide in your presenters whether to show an element or not. If you
> want, you can store all your authorizations as an Enum and then you could
> customize your widgets with a "setRequiredAuthorization()" method, which
> could be passed in from UiBinder via <someTag
> requiredAuthorization="{FOO_AUTH}" />. However, ideally you'd keep your
> views (UiBinder) dumb and leave that authorization checking to a higher
> level.
>
> Of course, the kicker here is to secure the backend calls. I suggest
> @Secured or @PreAuthorize annotations to secure your methods, which works
> out of the box with Spring Security.
>
> Sincerely,
> Joseph
>
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
