About OAuth Client data instances
|
|
OAuth is a standard framework that enables secure, delegated access to services via HTTPS. OAuth 2.0 is the next evolution of the OAuth protocol. There are several grant types in the OAuth 2.0 specification.
OAuth provides tokens (sometimes called "valet keys") giving access to your data hosted by a given service provider. Each token grants access to a specific site for specific resources, for a defined period of time.
Your applications can act as an OAuth 1.0 consumer/client. As a result, your application can access private resources stored in external web sites like LinkedIn, which support the OAuth 1.0 protocol.
Create an OAuth Client data instance as part of the process to allow your application to securely access Web Service APIs such as those provided by LinkedIn.com, Twitter.com, and Flickr.com, without storing or disclosing individual users' names and passwords. As an example, you might want to query your LinkedIn account for information about your connections there to help you build relationships with customers you connect with through your application.
Each external application handles OAuth in its own way, and you should consult the API guide for the application you wish to work with. At a high level, the process involves these steps:
OAuth Client data instances are referenced on the OAuth 1.0a tab of Authentication Profile rule forms.
Activities that submit information to the application you want to connect to, and receive tokens back from that application, use data stored in the OAuth Client data instance.
Use the Records Explorer to see all the Oauth Client data instances in your system.
The Data-Admin-Security-Oauth-Client class contains Oauth Client data instances. They are part of the Security category.