Setting General Permissions

Access the Permission Lists - General page (select PeopleTools, and then Security, and then Permissions and Roles, and then Permission Lists and click the General tab).

This example illustrates the fields and controls on the Permission Lists - General page.

Permission Lists - General page
Field or Control Description

Navigator Homepage

Select a graphic representation of a business process that is displayed by PeopleSoft Navigator. For each security profile definition, you can specify a map to be displayed on startup.

If this is the user profile's PeopleSoft Navigator homepage permission list, the system is passed this value at runtime.

Can Start Application Server?

Select to enable user profiles with this permission list to start PeopleSoft application servers.

Note: This setting also applies to starting PeopleSoft Process Scheduler servers.

Typically, you will create a user profile that is dedicated to starting application servers. When you define an application server domain, one of the parameters you specify in PSADMIN is the PeopleSoft user ID (and password) for that profile, which must be associated with at least one permission list that has this option enabled. The user ID and password are stored in the Startup section of the PSAPPSRV.CFG file, which Oracle Tuxedo reads when the application server is started.

In many installations, an application server starts with an automated process. A user profile with this property enabled should not be used by an actual user who signs in to the application server and starts it by submitting the appropriate commands.

Note: Password controls do not apply when a password is used for two-tier activities like starting application servers. They apply only when the password is used to sign in over three-tier connections.

Important: For a given user profile, the password controls that you set for account lockout (maximum logon attempts) and age (expiration) apply to three-tier and web sign in only; they do not apply if the user profile is used for two-tier activities like starting an application server or process scheduler. However, make sure that you do not use the same user profile for both types of activities. When you use it for both three-tier and web sign in, the profile becomes subject to the account lockout and age controls, which prevents it from completing the two-tier activities.

Allow User ID/Password to be Emailed?

Select to enable user to receive forgotten user IDs or passwords through email.

At some sites, the security administrator may not want passwords appearing unencrypted in any email. You implement this feature by permission list. None can use it, some can use it, or all can use it, depending upon your implementation. Users who do not have the proper authority receive an error message if they attempt to have a new password or user ID emailed to them.

See Working With Passwords.

See Configuring User Profiles for Forgotten User ID Emails.

Never Time-Out and Specific Time-out (minutes)

Select the number of minutes of inactivity allowed at a terminal before the system automatically signs the user out of the PeopleSoft online system. Inactivity means no mouse clicks, keystrokes, import, file print, or SQL activity. The default time-out minutes setting is Never Time-out.

Note: Time-out limits are also controlled at the web server and application server levels.

If you select Never Time-out, an inactive user is never automatically signed out. Otherwise, select Specific Time-out (minutes) and enter the appropriate value in minutes. A custom time-out interval:

  • Must be a positive integer.

  • Cannot contain edit characters, such as commas or a $.

  • Must be a SMALLINT in the valid range allowed for this field (0-32767).

Entering a value of zero (0) is equivalent to selecting Never Time-out.

In order for the Never Time-Out or Specific Time-out (minutes) settings to work for a user, every permission list for that user profile must have a non-zero value set for Specific Time-out (minutes). The time-out that will apply to the user profile is the highest value in all the permission lists.

Any user profile with the PeopleSoft Administrator Role will ignore the time-out settings on any other permission list.

Note: Because timeout limits are also controlled at the web server level, you will need to change the web server timeout values also. See Portal Technology: Configuring Portal Security and System and Server Administration: PIA Timeouts.