Contents

Node Best Practices

  • Never ever use the “Authentication Option” of “none”.
    • This means that there is no password required to execute web services against that node.
  • Make sure your anonymous node is secure
  • Create a new NODE for each application you are integrating with.
    • A node is a representation of an external system or integration client. They are free to create so do not share them.
  • Each Node should have a unique “Default User ID” configured on the node.
    • When using Node authentication (not PS_TOKEN), This ensures that the node is locked down to only service operations specifically granted to that end-point.
    • For inbound service operations that perform updates in PeopleSoft, any audit fields like LASTUPDOPRID will be marked with this unique user ID making troubleshooting and auditing more clear.
  • The OPRID you create for the node should have a clear naming standard like {ORG_PREFIX}_{APP_NAME}_NODEUSER. For example, CHG_SSOSYSTEM_NODE_USER.
    • This OPRID should not have rights to login to the system. Do not grant any weblib security.
    • This OPRID should not have a password on PSOPRDEFN.
    • Make sure this OPRID only has very limited access to only the service operations that the integration partner should execute.
    • May need component interface and data security depending on the web services.
    • NEVER use a super-user OPRID on a node.
  • When configuring Service Operation Routings be sure to never us “Any to Local” routings. Always explicitly define your nodes in the routings to tell the systems what integrations go where.
    • This can be self documenting of who uses the integration as well as more secure if someone improperly configures a node.

You can read more about nodes in the Node Chapter.

Author Info
Chris Malek

Chris Malek is a PeopleTools® Technical Consultant with over two decades of experience working on PeopleSoft enterprise software projects. He is available for consulting engagements.

Work with Chris
PeopleSoft REST APIs in Minutes, Not Months
PeopleSoft Simple Web Services (SWS)

SWS turns SQL into production REST APIs — ready for AI, modern apps, and partner integrations. One install, unlimited potential.

  • Configuration-driven, no coding required
  • JSON, XML, and CSV output
  • Works across all PeopleSoft pillars
  • Built on 25+ years of PeopleSoft expertise
Read More & Purchase
Looking for pain-free PeopleSoft web services?
PeopleSoft Simple Web Services (SWS)

A powerful PeopleSoft bolt-on that makes REST web services easy. You bring the SQL, SWS handles the rest.

  • Go from idea to production in minutes
  • Zero code migrations after install
  • JSON, XML, and CSV output supported
  • No PeopleCode or Integration Broker expertise required
Read More & Purchase
Stop Building PeopleSoft Web Services the Hard Way
PeopleSoft Simple Web Services (SWS)

Traditional PeopleSoft web services cost $3,600–$13,000 each to develop. SWS deploys production REST APIs in under 5 minutes through configuration alone.

  • No PeopleCode or Integration Broker expertise required
  • Works across Campus Solutions, HCM, and Financials
  • Built-in pagination, caching, and nested data structures
  • Trusted by institutions across higher education and government
Read More & Purchase
PeopleSoft REST APIs for AI, Modern Apps, and Integrations
PeopleSoft Simple Web Services (SWS)

Turn PeopleSoft data into clean REST APIs for AI integrations, modern applications, and vendor data feeds. Configuration-driven — no PeopleCode required.

  • Deploy production APIs in under 5 minutes
  • AI and LLM ready (RAG, chatbots, intelligent search)
  • JSON, XML, and CSV output
  • Zero modifications to delivered PeopleSoft objects
Read More & Purchase