Showing posts with label Security. Show all posts
Showing posts with label Security. Show all posts

What are the different ways we can set up the portal security to access component in portal?


 1) Structure & content
2) Menu import

3) Register component

What are the rules used by the system to determine whether a user is authorized to update an object?

The user should have the permission to update the object. This is given by the Definition security. The group which holds the object should be added to the permission list of the user in update mode.

How to authorize the user to run a process or report?

To authorize a user to run a process, the process group which contains the process or report should be added to the permission list of that user. 

Before accessing a people soft application what levels of security must be passed through?

a) Field level security
b) Row level security
c) Maintain security
d)definition security

e) Portal security

What are the different ways to setup row level security?

We can setup row-level security using a SQL view that joins the data table with an authorization table. and By having Query search for data using a query security record definition. The query security record definition adds a security check to the search.

What are all the various types of SJT?

• SJT_CLASS
• SJT_CLASS_ALL
• SJT_PERSON

• SJT_DEPARTMENT

What are all the Access types for Recruiting Job Opening security sets?

• RS Company
• RS Business Unit
• RS Department ID
• RS Location

• Recruiting Team

What are all the Access types for People without jobs security sets?

• POI Business Unit
• POI Location
• POI Institution

• Person of Interest

What are all the Access types for People with jobs security sets?

• Job department tree
• Job location
• Jon business unit
• Job Company
• Job regulatory region
• Job salary grade
• Person organisation
• Department ID – non tree

• Company – Pay group

What are all the Access types for Department security sets?

• Departments by Tree
• Departments by non – tree

• Departments by set id

What are all the methods for assigning Data Permission Access to Permission List?

• Tree based data permission security

• Role based data permission security

What are all the default Permission List used while creating the User ID?

• Navigator Homepage Permission List
• Process Profile Permission List

• Primary Permission List

What are all the default programs you need to run after the creating the user profile?

• Refresh SJT CLASS ALL
• Refresh Trans. SJT tables

• Refresh SJT OPR CLS

What are all the People Tools Security?

• Permission List
• Roles

• User Profiles

When to use Employee ID and Operator ID.

Employeeid is employee id which is maped to ur profile
Oprid is the profile name with which u logged in ( if u have loged in with a id called PS or VP1, then Oprid is PS/VP1 and employeeid is the emp id which is mapped to the user.

 %EmployeeId  - returns an uppercase character string containing the Employee ID of the user currently logged on. This is typically used to restrict access to an employee's own records

%OperatorId - returns an uppercase character string containing the operator currently logged on. This is typically used to restrict access to records or fields to specific operators.


%UserId - returns a character string containing the user currently logged on. This is typically used to restrict access to records or fields to specific users. 

What is the use of primary permission list in user profile?

     Primary permission list is used for mass change and definition security 

What is primary permission list?( seen in user profile above row level security )

 1.) The use of Permission lists, Roles, Data Permissions and User Profiles are now the heart of PeopleSoft security. Data Permissions (Row Level Security), Primary Permission lists (Primary Class) and Permission lists (Class) are all created within the same page for easy maintenance.  Though all levels of permissions are maintained on the same page, be aware that each of these permissions has a different use in the system. Steps must be taken to ensure they are used in the correct situations. 

PeopleSoft 8 requires a new naming convention be followed.  All data permissions have to be prefixed with “DP” and all primary permission lists have to be prefixed with “PP”.  All pages used with these permissions have a search record that filters by these prefixes.  One step of the upgrade process copies the old values into the permissions tables and should have a “PP” or a “DP”. Once established, the new values with the new prefixes, clean up the old values can be accomplished using SQL. Sometimes the only way to create the new value in PeopleSoft 8 is to use SQL and change one of the old values to the new standard, updating the user profile to match the required changes. 

Primary permission lists are used to default field values for each user in PeopleSoft. The primary permission lists are set up on the permission list page just like any other permission list. What’s unique about them is that no security is added to this permission list. Though this permission list appears on the User Profile, none of the security will be used in the profile. The permissions will not carry forward to the User Profile unless the permission list is passed through a role.  It’s better to leave the primary list as a blank placeholder for primary permission default values only.  

Global security is a maintenance page that enables the country specific flags associated with all global pages to be functional.  The global security is associated with the Primary permission list. If not prefixed with “PP” or “DP”, the same problems may occur when accessing global security to maintain these flags.  There is always a large group of non-usable information in the table that doesn’t need to be there after the upgrade process is run.  Using SQL, update one row to the new “PP” row. Clean up the rest of the rows by adding “PP” or deleting. (Make sure the search record for this page is set to ORPDEFN_SRCTY4.) 

2) PeopleSoft determines which data permissions to grant a user by looking at the users'   Primary Permission List and Row Security Permission List. Which one is used varies  by application and data entity (Employee, Customer, Vendor, Business Unit etc). 

3) Other than role-permission lists, there are 4 permission lists which are directly attached to the user and not via role.

Those are set on the user profiles page. One of them is primary permission list.

4.) Create a Permission list that will give access only fo a couple of Business Units. Now this can be done by creating suitable Primary Permission List.