1. WMS REST API Guide
  2. Steps to Login via a Custom App that uses the Redwood Mobile API

Steps to Login via a Custom App that uses the Redwood Mobile API

Note: The published Redwood Mobile API, can only be used from native Android, iOS, Java or other non-browser based custom applications. It is not supported from custom web applications.
  1. The custom app should either start the process below automatically on login or must have a Login via SSO button, which when clicked starts the sequence of events.
  2. The custom app should use the authorization code grant type mechanism using the client ID, client secret and Scope to fetch an authorization token from WMS IDCS using the authorization URL provided by IDCS
    • This should cause a redirection to the IDCS authorization URL web page, in which the user can login with their WMS IDCS username and password. This approach negates the need for the custom app to have its own login page.
  3. The retrieved token should be saved by the custom app.
  4. The custom app makes the get next RW mobile API call using this token which will return the JSON for the page to be rendered by the custom app.
  5. It is up to the customer to determine how to render the UI based on the JSON. The details of the JSON can be self-discovered using the Oracle delivered Redwood Mobile web app. The Group setting Easy trace mode should be turned on and then the browser should be put into developer mode and opened to the network tab. Open the Redwood Mobile URL (https[:]//{cluster}.wms.ocs.oraclecloud.com/{env-name}/index_pwa) and wait for the RF menu to be rendered.
  6. In the network tab of developer tools, look for the redwood mobile internal API. Although this API is different from the published one, this can be used to understand the request and response and map the JSON visually to what is rendered on screen. Do NOT use the specific API shown in the developer toolbar. It’s only for internal Oracle use and may change at any time. Customers must use the published Redwood Mobile API.