I have modified my SecureScreen servlet to look like this:
if (acl.hasRole("turbine_root) || acl.hasRole("technician"))
return true;
However, no session is being established. It logs in the user. I can see this
because it puts an entry in the database's "last login date" field.
It was my understanding that secure pages were dumped through the LoginUser action and
that was part of FluxLogin. Is this incorrect?
Does anyone have any other possible solutions to this problem?
Thanks.
-------------------------------------------------------------
Darin Wilcox
Web Engineer
College of Nursing
University of Utah
585-7332
>>> [EMAIL PROTECTED] 10/17/01 09:31AM >>>
Did you check the method isAuthorized in SecureScreen. The version that
I have only allows you to get in if you have the turbine_root role. You
can freely change this method to give access permision according to
roles, permissions, or groups. Apparently it is very flexible, but you
have to redefine the method isAutorized() according to your needs.
--
Humberto
-----Mensaje original-----
De: Darin Wilcox [mailto:[EMAIL PROTECTED]]
Enviado el: Tuesday, October 16, 2001 10:16 PM
Para: [EMAIL PROTECTED]
Asunto: Flux Login Issues
I am currently running tdk 2.1 on Solaris with an Oracle server. I have
a problem allowing access to any user that does not have a role of
"turbine_root" and in the "global" group when I extend SecureScreen.
Is there something specific regarding the creation of users and groups?
I have been manually adding them into the database and giving all roles
"admin_users" permissions, but this doesn't seem to be working. Is
there something else behind the scenes I am missing?
For instance, if I want to create a role called 'technician' with
'admin_users' permissions, what are the steps? or is this even possible?
Thanks
-------------------------------------------------------------
Darin Wilcox
Web Engineer
College of Nursing
University of Utah
585-7332
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
