Hi all,
I have an application that's been in use for the last 6 months or so
and will be going into production 2 months. I've now see two
instances of the problem described below and I'm fairly lost on how it
could possibly happen.
The client first needs to login. When the server authenticates
Apologies, the most recent error was captured in FF4.
On Aug 11, 6:02 pm, sunny...@gmail.com sunny...@gmail.com wrote:
Hi all,
I have an application that's been in use for the last 6 months or so
and will be going into production 2 months. I've now see two
instances of the problem described
How manage authorization and authentication?
2011/8/11 sunny...@gmail.com sunny...@gmail.com
Hi all,
I have an application that's been in use for the last 6 months or so
and will be going into production 2 months. I've now see two
instances of the problem described below and I'm fairly lost
Authentication is done once at login. The user credentials are sent to
the server using GWT-RPC, and the server authenticates using LDAP.
Once authenticated, the user loads the full user object into the
hashmap keyed by session IDs. Part of this user object contains a
hashmap of permissions
I tell you because we have similar issue in the past (not with gwt) and is
relate to authentication and authorization mechanism. We do the
authentication with a servlet and don't put filters.
Both authentication and authorization at now is made by filters. All
operations is made by filters in
Thanks. I don't believe there is a clustering issue as the application
isn't running on a clustered environment, and its only one of two
applications deployed on the server's Tomcat instance. Neither have
anything to do with each other.
The application is also an internal one that's used by 25
