Securing Provider REST Service Operations

This section discusses securing provider REST service operations.

Requiring Secured Inbound Consumer Requests

When you create provider REST services you can set the level of security with which inbound service operations must be sent using options in the Req Verification drop-down list on the Service Operations page. If you set a required inbound security level and inbound messages do not meet the requirement, the messages are rejected.

The following security levels are supported for provider REST service operations:

  • Basic Authentication.

  • Basic Authentication and SSL.

  • None. (Default).

  • OAuth2 Authentication

  • OAuth2 Authentication and SSL

  • PeopleSoft Token

  • PeopleSoft Token and SSL

  • SSL.

See Security Administration: Understanding OAuth 2.0.

Setting Permissions for Provider REST Service Operations

Provider REST service operations are secured using permission lists. The process for setting permissions for provider REST service operations is identical to the process for setting permissions for non-REST service operations.

See Setting Permissions to Service Operations.

See Integration Broker Administration: Validating Security on Inbound Integrations.