Peoplesoft Pagelet Authorization Error
consultants. This blog also contains few useful tips and tricks, solution to some of the standard PeopleTools and HCM errors as well peoplesoft authorization error contact your security admin as few solutions on Oracle and Crystal Reports. Authorization Error in PeopleSoft PIA's peoplesoft iscript authorization error "Top Menu Features Description" pagelet In PeopleSoft HCM 9.1 PIA, there is a new pagelet which displays the "Top Menu Features Description". This pagelet is accessible for the users having the permission list - PTPT1000. However in real time, rolling out this PTPT1000 permission list for production users is not preferred. We instead clone this permission list and create a new one removing the other privileges in PTPT1000 permission list which we would not want a normal end user in production to be exposed with. When cloning of the Permission list is not done properly, it results in several issues. Error Message:"Authorization Error - Contact your security administrator." One such issue is the Top Menu Features Description pagelet showing message as"Authorization Error - Contact your security administrator."This issue is common in PeopleSoft HCM 9.1 or in PeopleSoft applications with PeopleTools 8.50, 8.51, 8.52 and 8.53. Cause: This issue is with the cloning of permission list PTPT1000. For users with roles having PTPT1000 permission list(generally super users) will have no such issue. Solution: The web libraries defined for portal will have to be associated correctly with the newly created (cloned) permission list with proper access. To resolve this error message, make sure that this web library WEBLIB_PT_NAV is added to the permission list and given Full Access. And that solves it!!! on 10/10/2010 12:59:00 AM Email This BlogThis! Share to Twitter Share to Facebook Share to Pinterest Labels: PIA , Security 7 comments : AnonymousDecember 12, 2011 at 7:44 PMthanksReplyDeleteKaliga'sKitchenJuly 20, 2012 at 8:07 PMThanks.. This has helped us..ReplyDeleteDerekDecember 14, 2012 at 8:43 PMVery Helpful! ThanksReplyDeleteAnonymousDecember 21, 2012 at 4:37 AMThis Weblibrary is there but I am still getting the same message.IT is a great place to start.Thank you.ReplyDeleteAnonymousDecember 22, 2012 at 1:15 AMI posted yesterday it w
May 24, 2011 User does not see a Pagelet on a HomePage Even though user has a access to Pagelet, he does not see it on a HomePage. This indicates that WebServer Pagelet cache is corrupt. Only way to make it work correctly is to restart the webserver. But if this happens in the middle of a day, you can use this trick to force the webserver Homepage pagelet cache refresh. Add a new page to Homepage tab as a required fix. (PeopleTools -> Portal -> Structure and Content -> Portal Objects -> HomePage -> Tabs - Home). Go to the Tab Content Tab and add the new Pagelet as http://peoplesoftwiki.blogspot.com/2010/10/authorization-error-in-peoplesoft-pias.html require fix and select the column, usually the last column. Save it and relogin with user id who is complaining that he is not able to see the pagelet. He should now see the missing pagelet. Remove the newly added pagelet, as it is no longer needed. You can use the following sql to determine what pagelet user has access to . SELECT * FROM PSPRUHTABPGLT where oprid = '7420060' http://peoplesoftexperts.blogspot.com/2011/05/user-does-not-see-pagelet-on-homepage.html ORDER BY portal_col_num,portal_row_num; For further reference, Go to MOS (My Oracle Support) and see the following resolution. E-PORTAL: What Are The Tables Used By Portal Technology? [ID 651342.1] Posted by Ketan Kothari at 2:59 PM Labels: Portal No comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Google Talk Labels 8.50 (2) 8.53 (9) App Degigner (2) AppEngine (5) Application Designer (2) Application Engine (2) Application Server (1) BI Publisher (3) Browser (2) chrome (1) Cisco ACE (1) Compare Reports (1) Component Interface (2) Configuration (1) Crystal (1) Databas Link (1) DSS 3.1 (1) DST (1) Enterprise Portal (2) ExcelToCI (3) FireFox (1) IE9 (1) image (1) Install (1) Integration Broker (4) Internet Explorer (1) iOS (1) ios9 (1) iPad (1) iPhone (1) Java (1) LDAP (1) LoadBalancer (1) Metalink (1) Microsoft (2) Oracle (4) Page (1) PCI (1) PeopleCode (8) PeopleSoft (3) PIA (6) Portal (2) Portal Interaction Hub (1) Process (6) Process Scheduler (3) PT8.50 (2) Query (6) Remote Pagelet (1) Reports (1) REST (1) safari (1) Scheduling (1) Security (6) Server Administration (1) SHA256 (1) Signon (1) SSL (1) Stylesheet (1) Support (1) TLS1.2 (1) Trace (1) Tuxedo (1) Unified Navigation (1) Web Services (2) WebLogic (3) Windows7 (1) Wor
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about http://stackoverflow.com/questions/11765000/peoplesoft-8-52-menu-authorization-error Stack Overflow the company Business Learn more about hiring developers or posting ads with https://docs.oracle.com/cd/E55243_01/pt854pbr0/eng/pt/tprt/task_Step6SpecifyingPageletPublishingOptions-017477.html us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Peoplesoft 8.52 menu authorization error up vote 0 down vote favorite With any kind of authorization error account besides administrator, we get an authorization error for the drop down menu. (And other pages) The users do have the PTPT1000 access with WEBLIB_PT_NAV and full access to every iscript within that weblib. We also performed a security sync and cleared the cache. Any ideas on what is wrong and how to fix this? peoplesoft share|improve this question asked Aug 1 '12 at 18:06 Kevin Moore 12914 add a peoplesoft pagelet authorization comment| 1 Answer 1 active oldest votes up vote 0 down vote An Administrator in PeopleSoft does not have any special access other than what has been granted through Security Administration. I would try visually comparing the two accounts, and if that proves too arduous, then clone the administrator account and incrementally remove roles until you find the one that is granted the required access. Just to be on the safe side I would delete the app server and browser cache as the first step. Good luck! share|improve this answer answered Aug 13 '12 at 17:29 ardochhigh 1,91132646 Thank you for the reply. As a quick temporary fix we gave the user all the web libraries full access which obviously worked. I was hoping that someone knew the exact permission list and web library that controlled this. And while we are on the topic, I also need to know the permission list/web library for drag and drop functionality for pagelets. Thank You. –Kevin Moore Aug 13 '12 at 18:04 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up using Google Sign up using Facebook Sign up using Email and Password Post as a guest Name Email Post as a gu
creation process. Understanding Caching Options, Press Enter to expand Enabling caching improves performance because after the pagelet is stored in the cache memory, the next time the pagelet is accessed, the information is retrieved and displayed from cache memory instead of requiring a trip to the server. Three caching options exist: Private. Private caching is user-based; pagelet caching is stored per user. For example, if user A accesses the pagelet, only user A will access the pagelet from the cache. Public. Public caching is application-based; pagelet caching is stored per web server instance. For example, if a user accesses the pagelet using web server instance 1, only other users accessing the pagelets using web server instance 1 will access the pagelet from the cache. Role. Role caching is role-based; pagelet caching is stored per user role combination. For example, if user A has membership in roles 1, 2, and 3, only another user with all roles 1, 2, and 3 will access the pagelet from the cache. Content Reference Attributes If you enable caching, Pagelet Wizard adds the following attribute information to the pagelet content reference: Name: PSCACHECONTROL Label: PSCache-Control Attribute value: Caching Type field value;max-age=Minutes to Cache field value For example, Public;max-age=30. After the pagelet is saved and registered, you can use Pagelet Wizard to alter caching options in the same way that you can alter other registration information. However, altering caching option values requires that you reregister the pagelet. See Administering Content References. Common Elements Used in This Section, Press Enter to expand Field or Control Definition Enable Caching Select to enable caching for the homepage or template pagelet. Selecting this option displays the Caching Options group box. Caching Type Private: Select to enable user-based caching. Public: Select to enable application-based caching. Role: Select to enable role-based caching. Minutes to Cache Enter the number of minutes th