RE: WebFacing security

Rick,

If you use a "prep" program for users (we use routing data but initial
program will work) when they log on you and either check the environment for
webfacing or enter qqfinvoker and monitor message for a failure and then
just push the user to their normal 5250 entry point. One issue remains,
qqfinvoker locks the user message queue, and if a web project is the first
logon it does not release it. Also you would have to add code to your web
project to see the message queue. I haven't done this yet because I just
found out I need wdsc Advanced to get system screen support.
 

Michael P. Gibbons
Manager of Programming & Technical Services
MARYWOOD UNIVERSITY
2300 Adams Ave. 
Scranton, PA 18509



-----Original Message-----
From: Rick.Chevalier@xxxxxxxxxxxxxxx
[mailto:Rick.Chevalier@xxxxxxxxxxxxxxx]
Sent: Monday, November 15, 2004 10:22 AM
To: wdsci-l@xxxxxxxxxxxx
Subject: RE: [WDSCI-L] WebFacing security


This may need to be a separate thread but since the subject is WebFacing
security here goes.

We recently got all the pieces together to try web facing in our shop.  It
came as quite a shock to learn that end users could not use web faced
applications is there user profile is set to limited capability.  In order
to use a web faced application we have to allow end users to enter commands
from a command line.  Our security department won't let this happen.

Are we missing something?  Has anyone found a way around this limitation?

Rick


_______________________________________________
This is the Websphere Development Studio Client for iSeries  (WDSCI-L)
mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.