Author Info
Chris Malek

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

About Chris Work with Chris
Looking for pain-free PeopleSoft web services? 😀
PeopleSoft Simple Web Services (SWS)

Introducing a small but powerful PeopleSoft bolt-on that makes web services very easy. If you have a SQL statement, you can turn that into a web service in PeopleSoft in a few minutes.

Read More & Purchase
Contents
0. About Book
1. Getting Started
2. Service Operations
3. REST Services
4. Security
5. Monitoring & Administration
6. Example Service Operations
7. Data Encoding/Decoding
8. Nodes
9. Services Delivered by Oracle
10. Listening Connectors
11. Handlers
12. Target Connectors
13. Syncing Data Between PeopleSoft Systems
14. API Gateways
15. Best Practices
Search

Node Best Practices

  • Never ever use the “Authentication Option” of “none”.
  • 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 across projects or integrations. New server/vendor/etc, create a new node.
  • 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 use “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.

Copyright 2018-2024 Cedar Hills Group, Inc. All rights reserved.