kastanek
Well Known Member
Hello List!
I've seen thread on this particular topic fairly regularly and there never
seems to be a definitive answer. Most people talk about using Windows
based security on the server side which adds complexity and another layer
to administer. Other people talk about renaming the IEXPLORE.EXE program
which doesn't work either since Windows just reinstalls it when it needs
it.
Here's what I have just come up with and it seems to be working just fine.
I'll run it for a while and let you all know if there's any issues with it
that I can find.
Internet is accessible through three main areas: The Task Bar in the
Solution Explorer, The Action bar in all OneWorld Applications and the
TOOLS Exit bar in every application.
The Task Bar access can be secured out using Solution Explorer Security in
Security Workbench - no sweat. The trick has been securing it out of the
other two areas. Here's how I did it.
The application that runs behind the scenes and controls the Tools Exit as
well as the Action Bar is called PHYPER.
From OMW:
- Check out PHYPER
- Design
- Design Tools
- Start Form Design Aid
- Select form: "Find/Browse"
- Select FORM from the menu bar and click "Menu\Toolbar Exits"
- Scroll to "Exit to Internet Browser" and highlight it
- Click Select
- Under STATE select DISABLED
- Click OK
- Click Close
- Repeat the last 7 steps for forms: Header/Detail and Headerless Detail
- Save the forms
- Check the object back in and promote as required.
After the forms are validated the change will be visible on your
development machine. To make these changes available to every fat client
you need to do a full build. Update builds did not work for me. Probably
because I was missing something but the full build worked just fine.
Internet Explorer options are now greyed out for all fat clients, Terminal
Servers (this was a security hole to the C: drive as well) in both
Solution and OneWorld Classic explorers.
I hope this works for you guys. I'd love to hear some feed back as to any
issues that this may cause or success you get with this.
Regards,
Gerald.
Oneworld XE B7333 sp 18.1 update 3 AS/400 + W2k
I've seen thread on this particular topic fairly regularly and there never
seems to be a definitive answer. Most people talk about using Windows
based security on the server side which adds complexity and another layer
to administer. Other people talk about renaming the IEXPLORE.EXE program
which doesn't work either since Windows just reinstalls it when it needs
it.
Here's what I have just come up with and it seems to be working just fine.
I'll run it for a while and let you all know if there's any issues with it
that I can find.
Internet is accessible through three main areas: The Task Bar in the
Solution Explorer, The Action bar in all OneWorld Applications and the
TOOLS Exit bar in every application.
The Task Bar access can be secured out using Solution Explorer Security in
Security Workbench - no sweat. The trick has been securing it out of the
other two areas. Here's how I did it.
The application that runs behind the scenes and controls the Tools Exit as
well as the Action Bar is called PHYPER.
From OMW:
- Check out PHYPER
- Design
- Design Tools
- Start Form Design Aid
- Select form: "Find/Browse"
- Select FORM from the menu bar and click "Menu\Toolbar Exits"
- Scroll to "Exit to Internet Browser" and highlight it
- Click Select
- Under STATE select DISABLED
- Click OK
- Click Close
- Repeat the last 7 steps for forms: Header/Detail and Headerless Detail
- Save the forms
- Check the object back in and promote as required.
After the forms are validated the change will be visible on your
development machine. To make these changes available to every fat client
you need to do a full build. Update builds did not work for me. Probably
because I was missing something but the full build worked just fine.
Internet Explorer options are now greyed out for all fat clients, Terminal
Servers (this was a security hole to the C: drive as well) in both
Solution and OneWorld Classic explorers.
I hope this works for you guys. I'd love to hear some feed back as to any
issues that this may cause or success you get with this.
Regards,
Gerald.
Oneworld XE B7333 sp 18.1 update 3 AS/400 + W2k