Kaizen 133 Deciding on the type of applications self client or server based
Welcome back to the Kaizen series!
In this week's post in the Kaizen series, we will discuss self client and server-based clients in Zoho CRM. We will explain these two client types in separate videos, along with their practical application using Java SDKs.
How authorization is done in Zoho CRM?
In Zoho CRM, the protocol used for authorization is OAuth 2.0. OAuth 2.0 is an industry standard protocol specification that enables third-party applications or clients to gain delegated access to protected resources in Zoho via an API.
You can use self client when the app you develop is intended to communicate with your own Zoho account and it doesn't have a domain and redirect URL. You can also use this option when your application is a standalone server-side application performing a back-end job.
Scope
Scope is a set of permissions for which the token has to be generated for a client. OAuth2.0 scopes in Zoho CRM determine a client/web app's access rights to specific resources. Scopes dictate:
- Resource accessed (e.g., Users, Modules, Files)
- Permissible operations (e.g., ALL, READ, WRITE, CREATE, UPDATE, DELETE)
When you register an app in Zoho API Console, you typically choose a client type based on the type of usecase which you are trying to solve using the ap. The different client types available are
- Server-based
- Client-based
- Self client
- Non-browser-based
- Mobile-based
Self Client
When your application does not have a redirect URL or a web UI, operating solely in the backend without requiring user interaction, self client type is the appropriate choice. Consider that you have a legacy product management system and want to perform data sync between Zoho CRM and the system, then you must use the self client.
A self-client is commonly employed when both the application and Zoho services are managed by the same person, aiming to establish secure communication between them.
Here's a summary of the process of using self client type:
- Register your app as a self-client in the Zoho API Console.
- Obtain client details such as client ID and client secret.
- Specify the necessary scopes for your app to access CRM data.
- Obtain the grant token.
- Your app should then initiate API calls to Zoho Accounts to create access & refresh tokens using Zoho CRM SDKs
- Utilize this access token for API calls to Zoho CRM.
You can refer the sample code used in the video for data sync in the attached code.
Server-based Client
If you are developing an app that's intended for use by multiple Zoho accounts, you can use Server-based OAuth App. This app could be solving a special usecase for all Zoho accounts. The app should have both a dedicated backend server and web UI to handle the authorization process and the app's logic. The app redirects users to Zoho for the authorization process using a web browser. Users grant permission for the app to access their Zoho data on their behalf. The app will consume data for it's intended purposes on behalf of the user who authorized the app.
You can refer the sample code used in the video for lead management in the attached code.
We hope you found this post useful and improved your understanding. Let us know your thoughts in the comment section or write to us at support@zohocrm.com.
Further reading:
Previous Kaizen
New to Zoho LandingPage?
Zoho LandingPage Resources
New to Zoho Survey?
New to Zoho CRM Plus?
Deliver unforgettable customer experiences
New to Zoho CRM Plus?
Deliver unforgettable customer experiences
New to Zoho Marketing Plus?
Everything you need to run your marketing
New to Zoho Marketing Plus?
Everything you need to run your marketing
New to Bigin?
Topic Participants
Mable Mary M P
Vigneshwaran K
Sticky Posts
Extension pointers for integrating Zoho CRM with Zoho products #8: Upload and manage Zoho Workdrive folders and files from within Zoho CRM
Keeping records on your customers and business prospects is essential for tracking data, conducting follow-ups, and running a business smoothly. When you use two separate applications, and store relevant data in each, checking and tracking data becomesExtension pointers: Handle cases with personalized solutions using custom actions
In our last post, we detailed the steps involved in creating a custom action and the workflow from the developer and end user's side. Now let's look at a working example of how we can create a custom action and implement it in a Zoho CRM account to makeExtension pointers - Simple yet significant pointers #13: On change of field value for CRM variables
CRM variables provide global access to a variable across an entire extension. They also help in the storage of user-specific data provided by the user at the time of installation, which can later be fetched to perform data functionalities. Additionally,Extension pointers: Extend end-user benefits and allow personalization by implementing extensions with custom actions
From our earlier post on custom actions, we know that we can create templated actions, share them with end users, and allow them to reuse those actions to achieve personalized outcomes. In this post, we'll look at how custom actions make it easy for usersExtension pointers - Simple yet significant pointers #12: Functions for Zoho CRM extensions
Functions are essential in achieving logical functionality for an extension. You can easily code your functions in Deluge using drag-and-drop tools to meet your requirements. How to create functions for Zoho CRM extensions in Sigma Go to Sigma and select
New to Zoho TeamInbox?
Zoho TeamInbox Resources
Zoho DataPrep Resources
Zoho CRM Plus Resources
Zoho Books Resources
Zoho Subscriptions Resources
Zoho Projects Resources
Zoho Sprints Resources
Qntrl Resources
Zoho Creator Resources
Zoho WorkDrive Resources
Zoho Campaigns Resources
Zoho CRM Resources
Design. Discuss. Deliver.
Zoho Show Resources
Get Started. Write Away!
Writer is a powerful online word processor, designed for collaborative work.
Zoho CRM コンテンツ
-
オンラインヘルプ
-
Webセミナー
-
機能活用動画
-
よくある質問
-
Ebook
-
-
Zoho Campaigns
- Zoho サービスのWebセミナー