In this section: |
An administrator can manage security access according to individual users or a permission list. The decision for how to manage access is made as a connection option, and the two methods are mutually exclusive.
Regardless of the method for granting access rights to users, the process for managing security access is roughly identical. The administrator can affect security access for a user in the following ways:
How to: |
Before a PeopleSoft user can run reports against PeopleSoft, security access rights must be granted. The PeopleSoft connection does not automatically enable reporting for every user; instead an administrator must decide which users or permission lists have reporting access.
Note: Switching between users and permission lists is controlled by the Specify Security Access By drop-down menu under Security Parameters on the Update a PeopleSoft Connection window.
The Add Security Access to Connection window opens.
Note: If the security parameter of your connection is set to Class/Permission Lists, the window will allow you to Select Permission Lists rarther than Select Users.
Note: If you do not use a filter, or your filtered results are very large, the results may be truncated. Use a different filter to reduce the returned results.
The Add Security Access to Connection window opens.
Note: When you add users by Permission List, the users will only be granted access to Records with which the added Permission Lists are associated.
How to: |
You can remove security access from the PeopleSoft menu.
The Remove Security for Connection window opens.
Note: If the security parameter of your connection is set to Class/Permission Lists, the window will allow you to Select Permission Lists rarther than Select Users.
The PeopleSoft connection removes all references to these users or permission lists. After they are removed, the associated users cannot access PeopleSoft data through the PeopleSoft adapter.
How to: |
You can re-synchronize PeopleSoft security metadata when changes occur in the PeopleSoft environment. The following situations require resynchronization:
You do not need to run the security resynchronization routine if row-level security access has changed, based on the security table being updated. This type of security change will be enforced automatically and immediately. If the Query Security Record within a Record Definition has been changed, the synonym must be updated.
Note: A batch mechanism for resynchronization is also available that may be scheduled through a command line execution. For more information, see Advanced Administrative Topics.
Processing may take several minutes. Wait for a completion message before attempting other administrative tasks.
iWay Software |