Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Preparing OAuth 2.0 client registration for remote case types

Updated on March 29, 2022

To ensure that remote application from a consumer system can properly communicate with your producer system, prepare the OAuth 2.0 client registration in your producer system. As a result, you create a secure and reliable connection between your producer and consumer systems.

  1. In the navigation pane of Dev Studio, click Records.
  2. Expand the Security category, and then click OAuth 2.0 Client Registration.
  3. In the list of instances, open the Remotecasetype_Producer OAuth 2.0 client registration.
  4. In the form header, click SaveSave as.
  5. On the Save OAuth 2.0 Client Registration As form, in the Client Name field, enter a unique label, and then click Create and open.
  6. In the form header, in the RS section, click Edit, and then, in the text field, provide the ruleset to associate with your application.
    For example:
    Associating a rule with a ruleset
    A screenshot that shows a form with a text box to provide a ruleset for a rule
  7. In the Client Credentials section, download the client ID and client secret by clicking View & download, and then click Save.
    Note: You provide the client ID and client secret credentials when you register a remote system during creation of a remote case type. Ensure that you store the credentials safely.
    • Previous topic Configuring a producer system for remote case types
    • Next topic Preparing a token profile for remote case types

    Have a question? Get answers now.

    Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

    Did you find this content helpful?

    100% found this content useful

    Want to help us improve this content?

    We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

    Close Deprecation Notice
    Contact us