Assumptions and Prerequisites

This section describes the required configuration and process to authenticate Oracle Warehouse Management APIs using Identity Cloud Service (IDCS/IAM) when invoked from a custom web application. The APIs will be authenticated using the “Authorization Code” grant type in OAuth2.

This process will be useful for example if you are building a custom non-browser based application using the public Redwood Mobile API . See Empower Customer and Partner Customizations for Redwood Mobile for more information. Using this option, the custom app will not need to have its own login page and will not need to accept WMS user credentials. Instead it can redirect to the IDCS login page to login and obtain a token which can then be used to invoke the WMS API.

Here we are assuming that the IDCS for WMS is available. As of 2026, all customer environments have this.

Roles and Access Needed

• Administrative user access to WMS IDCS
• ADMIN role access to the following WMS configuration screens:
  • Custom Authentication
  • Users

Information You Must Collect

• WMS base URL
  • For example: https[:]//{cluster}.wms.ocs.oraclecloud.com/{env-name}
• WMS IDCS token endpoint
  • For example: https [:]//idcs-{wms-tenant-id}.identity.oraclecloud.com/oauth2/v1/token
• WMS resource scope as defined in WMS IDCS:
  • urn:resource:fusion:scm:logistics:wms:lgfapi/

Required Expertise

You need to have the required technical knowledge related to OAuth 2.0 authorization flows. We use POSTMAN as an example below, but behind the scenes it implements the specific calls that OAuth 2.0 demands and this document does not cover that information.