Create an OAuth setup

post

/fscmRestApi/resources/11.13.18.05/publicSectorGISOAuthSetups

Request

Header Parameters
  • If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
  • The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.
  • Contains one of the following values: true or false. If true, the server performs an Upsert operation instead of a Create operation. During an Upsert operation, the server attempts to find an existing resource that matches the payload. If a match is found, the server updates the existing resource instead of creating a new one. If not found or false (default), the server performs a Create operation. Note that the Upsert operation isn't supported for date-effective REST resources.
Supported Media Types
Request Body - application/json ()
Root Schema : schema
Type: object
Show Source
  • Title: Agency ID
    Default Value: 1
    The unique identifier for the agency.
  • Title: Application ID
    Maximum Length: 64
    The key value used to retrieve the web map security information.
  • Title: Application Secret
    The secret for the application ID. It is stored in the Oracle credential store.
  • Title: OAuth 2 Authorize URL
    The URL to request authorization from the user to access the secure web map.
  • Title: Description
    Maximum Length: 400
    The description of the OAuth setup.
  • Title: Expiration in Minutes
    The number of minutes for which a generated authentication token is valid.
  • Title: Secure Access ID
    Maximum Length: 64
    The unique identifier for the OAuth setup.
  • Title: OAuth 2 Token URL
    The URL to the web map that generates an access token for accessing the secure web map.
Back to Top

Response

Supported Media Types

Default Response

The following table describes the default response for this task.
Headers
  • If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
  • The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.
Body ()
Root Schema : publicSectorGISOAuthSetups-item-response
Type: object
Show Source
Back to Top