Scribd
Upload
10 views

Basic Security

This document discusses the different types of IDs and passwords used to access a PeopleSoft system, including operator IDs, connect IDs, symbolic IDs, and access IDs. It provides examples of each type of ID and describes where they are defined, what tables they relate to, and the level of access granted. It also summarizes the login process and relationship between the different ID types.

Uploaded by

Prashant Patil
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
10 views

Basic Security

This document discusses the different types of IDs and passwords used to access a PeopleSoft system, including operator IDs, connect IDs, symbolic IDs, and access IDs. It provides examples of each type of ID and describes where they are defined, what tables they relate to, and the level of access granted. It also summarizes the login process and relationship between the different ID types.

Uploaded by

Prashant Patil
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 5

Operator ID/Password

Example: PS/PS Defined in: PeopleSoft table of PSOPRDEFN, you will have many number of users Security: Set up within Roles and Permission Lists

Connect ID/Password
Example: people/peop1e Defined in: Configuration Manager and Database Security: Should have read-only rights to four tables in the database
Connects to DB and does a search of data Disconnects from DB after verifying the user and picking up the Access ID/Password info

Symbolic ID

Example: sa1 Defined in: PSOPRDEFN and PSACCESSPRFL tables. It is used as a place holder for only those two tables. Security: User is not known to PeopleSoft tables nor is it known to the Database

Database

Access ID/Password

Example: sa/sa Defined in: Database and is encrypted in the PSACCESSPRFL. Security: Full access to all the tables in the Database. This is the user name that will be known to the database, not the OPRID

Connects to DB with Access ID picked up by Connect ID. It stays connected to the database as the User till user logs out

What the Connect ID (people/peop1e) Looks At: PSSTATUS


OWNERID: sa TOOLSREL: PT 8.47

PSOPRDEFN
OPRID: PS OPERPSWD: xyz (encrypted) SYMBOLICID: sa1 ACCTLOCK: 0

PSACCESSPRFL
SYMBOLICID: sa1 ACCESSID: abc (encrypted) ACCESSPWD: def (encrypted)

PSDBOWNER (only for DB2 and Oracle)


DBNAME: HR89 DBOWNER: sa

A Look at the Login Process:


Connect ID/ Connect Pswd is picked up from Configuration Manager and used to check the four security tables

Oprid/ Operpswd

Once the verification against the four tables are done, then it disconnects and connects to the Application as the Access ID which has full rights to the database.

Access ID/ Password

Database

A Look at the Trace File (Resolution 709735):

Major Security Tables and Relationships(Does not include all) Users PSOPRDEFN PSOPRCLS PSROLEUSER PSROLEDEFN PSROLEUSER PSROLECLASS

Roles

Permission Lists

PSCLASSDEFN PSROLECLASS PSOPRCLS PSAUTHITEM (shows menu/page access)

Note: To get a complete list of Tables for each of these objects, look at the mvprdexp script found in the PS_HOME\scripts directory.

You might also like