Open topic with navigation

ibi™ Open Data Hub for Mainframe Connectors 1.0.8

# Satisfy Security Provider OPSYS Requirements

To run a server with security provider OPSYS, you must perform the following steps. You must do this once after installing and after each refresh of the server with fixes.

Set up tscom300.out as a root-owned SUID program:

Procedure
1. If the server is running, bring it down.
2. Log on to the system as root, or issue the su root command.
3. Change your current directory to the bin directory of the home directory created during the installation procedure.

   For example, type the following command:

       cd /home/iadmin/ibi/srv9190/home/bin

4. Change file ownership and permissions by typing the following commands:

       chown root tscom300.out

       chmod 4555 tscom300.out

5. Verify your changes by issuing the following command:

       ls -l tscom300.out

   The output should be similar to the following:

       -r-sr-xr-x 1 root iadmin 123503 Aug 23 04:45 tscom300.out

   Note the permissions and ownerships.

Result

When you start the server, it will now run with security provider OPSYS.

The chmod and chown steps will need to be repeated after any server upgrade since the tscom300.out file is replaced during an upgrade and the attributes are lost.

Note:

The server will issue RACROUTE REQUEST=VERIFY calls to authenticate users, so all users must have access to APPL MSO, which identifies our server.

If this Security Provider OPSYS step has been configured and the site later decides to switch to Security OFF, special steps must be taken to ensure the mode remains after a full server shutdown (where edastart -start is used to restart the server). The steps are:

1. After the server recycles from the change to OFF, use the WebFOCUS Reporting Server browser interface to open the environment configuration file of the server by clicking Workspace and expanding the Configuration Files folder, followed by the Miscellaneous folder.
2. Double-click Environment - edaenv.cfg to edit the file and add the EDAEXTSEC=OFF variable.
3. Save your work.

After the next full server shutdown, be sure to do an edastart -cleardir before restarting the server. This will clear any root-owned files that would prevent a security OFF server from starting.

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

ibi™ Open Data Hub for Mainframe Connectors

Copyright © 2021-2025. Cloud Software Group, Inc. All Rights Reserved.