Martin
I found jetspeed to be a very powerful single-signon tool
More importantly it enforces permissions associates actions to resources
Principals which can represent Users, Roles, and Groups
and finally policy which associates principals (the prople) to managed
resources (permissions)
http://portals.apache.org/jetspeed-2/multiproject/jetspeed-security/atz-spi.html
Feel free to let me know if you need any help with this,
Martin-
----- Original Message -----
From: "Martin Burkert" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List" <user@struts.apache.org>
Sent: Sunday, September 18, 2005 5:00 AM
Subject: Re: AW: How to pass Session variable to different Webapplication?
On Sat, 2005-09-17 at 14:51 -0400, Dave Newton wrote:
R. Markham wrote:
The original poster could use Struts modules or just consolidate configs
for each logical section of the app into their own files, or as Wendy
says use J. Random single sign-on method. If you really want to sahre
actual variables across webapps I'm not sure how you'd go about that
unless you stick things into a globally-accessible store and figure out
a way to update session vars in each webapp.
thx for your replies!
I think, it would be the best way, not to violate any specifications and
design patterns - just using only ONE webapplication divided into
several struts modules.
So i got an orientation what to do.
greetings martin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
