OAuth - Revision history

John: /* How does authentication work? */

2017-04-13T08:55:06Z

‎How does authentication work?

Matt at 13:17, 9 December 2015

2015-12-09T13:17:46Z

Matt: /* More Information */

2015-11-25T17:24:03Z

‎More Information

Matt: Created page with "
OAuth is an open protocol we support in WHMCS for allowing third-party applications to obtain limited access to the WHMCS service on behalf of use..."

2015-11-25T10:11:57Z

Created page with "<div class="docs-alert-info">OAuth is an open protocol we support in WHMCS for allowing third-party applications to obtain limited access to the WHMCS service on behalf of use..."

New page

<div class="docs-alert-info">OAuth is an open protocol we support in WHMCS for allowing third-party applications to obtain limited access to the WHMCS service on behalf of users.</div>

If you have an app or service that needs to interact with WHMCS on behalf of your users, you need to leverage OAuth.
WHMCS uses [http://oauth.net/ OAuth 2], an open specification, which allows users to authenticate with WHMCS to both verify their identity and give your app permission to access their data.

Once authorization is completed by a user, the OAuth process returns an access token to your app. The access token is a string generated by the WHMCS instance that you'll need to send with each subsequent API request to uniquely identify both your app and the end user.

There are several reasons we use OAuth. Most importantly, your app doesn't need to store or transmit the user's WHMCS password. OAuth also allows the user to authorize only a limited set of permissions and the user may revoke access at any time. This makes OAuth a safer and more secure form of API authorization for your users.

==OAuth 2 Workflow==

Here's how the process works.

#User presses a "Connect to WHMCS" button inside your app.
#Your app redirects the user to the WHMCS installation.
#The user logs into WHMCS and authorizes your app to access their WHMCS account using the permissions your app has requested.
#After the user approves your app, they'll be redirected back to your app with an authorization code.
#Your app can then use this authorization code to make a request for a re-usable access token which can be used to make subsequent requests to the WHMCS API. This takes place in the background and should not be visible to end users.

==More Information==

For more information, please refer to our [[OpenID Connect User Guide]] and [[OpenID Connect Developer Guide]].

@@ Line 30: / Line 30: @@
 The following API commands exist for interacting with OAuth/OpenID Connect credentials in WHMCS:
-* [[API:ListOAuthCredentials]]
+* [https://developers.whmcs.com/api-reference/listoauthcredentials/ ListOAuthCredentials]
-* [[API:CreateOAuthCredential]]
+* [https://developers.whmcs.com/api-reference/createoauthcredential/ CreateOAuthCredential]
-* [[API:UpdateOAuthCredential]]
+* [https://developers.whmcs.com/api-reference/updateoauthcredential/ UpdateOAuthCredential]
-* [[API:DeleteOAuthCredential]]
+* [https://developers.whmcs.com/api-reference/deleteoauthcredential/ DeleteOAuthCredential]
 ==More Information==
 For more information, please refer to our [[OpenID Connect|OpenID Connect User Guide]] and [[OpenID Connect Developer Guide]].

← Older revision		Revision as of 17:24, 25 November 2015
Line 20:		Line 20:
	==More Information==		==More Information==

−	For more information, please refer to our [[OpenID Connect User Guide]] and [[OpenID Connect Developer Guide]].	+	For more information, please refer to our [[OpenID Connect\|OpenID Connect User Guide]] and [[OpenID Connect Developer Guide]].

@@ Line 8: / Line 8: @@
 There are several reasons we use OAuth. Most importantly, your app doesn't need to store or transmit the user's WHMCS password. OAuth also allows the user to authorize only a limited set of permissions and the user may revoke access at any time. This makes OAuth a safer and more secure form of API authorization for your users.
-==OAuth 2 Workflow==
+==Related Features==
 Here's how the process works.
@@ Line 17: / Line 23: @@
 #After the user approves your app, they'll be redirected back to your app with an authorization code.
 #Your app can then use this authorization code to make a request for a re-usable access token which can be used to make subsequent requests to the WHMCS API. This takes place in the background and should not be visible to end users.
 ==More Information==
 For more information, please refer to our [[OpenID Connect|OpenID Connect User Guide]] and [[OpenID Connect Developer Guide]].

OAuth - Revision history

John: /* How does authentication work? */

Matt at 13:17, 9 December 2015

Matt: /* More Information */

Matt: Created page with "OAuth is an open protocol we support in WHMCS for allowing third-party applications to obtain limited access to the WHMCS service on behalf of use..."

Matt: Created page with "
OAuth is an open protocol we support in WHMCS for allowing third-party applications to obtain limited access to the WHMCS service on behalf of use..."