Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 2 years ago.
Improve this question
I need to integrate Zoho CRM to my react project(External application) and am new to react.Any one can give a solution? Is this integrating through back end or front end?
There is only one method which is through API's. Just go through the API docs. Api documentation has all the required information and also the sample json data. If they are not sufficient kindly try using Zoho postman collections.
Documentation: https://www.zoho.com/books/api/v3/
I understand that you wish to integrate React Project (External application) with Zoho CRM. However as now, There is no any method for direct integration of Zoho CRM - React Project. Hence, you can contact the API developer of ZOHO organisation & check the possibilities of completing the integration based on the business requirement using the API methods.
As previously mentioned you need to use the API's, the correct link for the CRM API is:
https://www.zoho.com/crm/catalyst/rest-api.html
A quote from Zoho:
"Zoho CRM offers the perfect collection of REST APIs and client libraries for building exciting new apps, for businesses of all sizes. The APIs are also secured by OAuth2.0 and API key methods to enable you to seamlessly integrate your Zoho CRM account with any third-party application.
Seamlessly push and receive information into your Zoho CRM account, or into any app that your team develops, using Zoho CRM API. Extract CRM data in JSON format, including any errors using simple HTTP methods."
I know this thread is quite old now but I still would like to contribute anyway.
Zoho's API is mostly used for extension apps or integrations; not if you want to add a user when the latter submut a form on your app; and their OAuth protocol is overkill, especially if you just want to add a new contact or whatever.
Plus their documentation is reaaaaaally organized (sarcasm obviously).
The simplest way to integrate any SPA with any Zoho apps is to use Zoho Flow (10$/mo or 25$/mo).
You can seamlessly create your own API using webhooks on it AND create workflow between any Zoho apps (CRM, Campaigns, Bookings and even third party apps.
You might be asking why should you pay an extra just to call their API?
Well it's just less of a nightmare, it's a small price to pay to make everything easy with Zoho
Related
I am trying to develop a REST API in spring boot and having React as the frontend. React will send GET or POST requests happening on the frontend to modify the MySQL DB in the backend via REST API. In my application, A user can have multiple companies inside the application and each company data is isolated from one another. I have come across Multi-Tenancy in Spring boot. How can I do this implementation for REST API ?? How can I configure my React application for this multi-tenancy?? Is Reactive Core in spring is useful??. Any resources where I can find these answers so that I can implement it. Or any other better way to implement this use case. Please, someone help me. Google results have confused me a lot
You could read a lot about this if you focus on little more details than a broad topic search in Stackoverflow
Here is one way you can achieve your requirement.
React App authenticates your end-users
There will be an API call from UI to get the list of accessible tenants
The list of tenants will be shown in the UI like in a dropdown
The end user will choose a tenant
Once chosen, untill a change next time, you will pass the selected tenant in all the API request headers so that you are identifying the tenant context of the user that is requesting for the data.
Regarding the data-isolation, you do have a lot of options explained in stackoverflow and people have multiple approaches depending on the multi-tenancy levels of course.
The above are the steps that you could achieve in any language (java in your case)
In case of choosing whether your API's are Reactive depends on the business needs. However you should be able to weigh the differences between the aync and reactive implementations, both have their needs, so identify the requirement and choose an approach that suits.
In case you need help in choosing the right approach for a given scenario, do share with us the scenario, how you did it and what you have issue / doubt and the community will be happy to help you.
We want to integrate docusign with one of our applications built in Sharepoint Framework (React).
Requirement is not to upload any e-signatures on external servers.
Question 1: How and where to prompt users for first time recording of their signatures?
Question 2: Can this be achieved inside the application without having the user go to their email and sign by redirecting them to docusign's server?
Any documentation on above questions would be much appreciated.
Great question Aquib. Both these things can be done using the DocuSign eSignature REST API. I would recommend you look at some of code examples that show how to do these things here:
https://developers.docusign.com/esign-rest-api/code-examples
Specifically, let me answer your questions:
1. Users can select their signatures the first time they are asked to sign, whether this is done via an integration or via direct send from DocuSign application. The system will remember your selection. If you have an account you can also go directly to your account and change this under "preferences".
2. You would want to use "embedded signing" which is what we call the ability to embed signing experience in your integration. You can see code examples for this here - https://developers.docusign.com/esign-rest-api/code-examples/code-example-embedded-signing
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
I know what I'm asking is quite vague, but Google has run up dry on this. I'm trying to build an API in Cloud Endpoints that hooks into a React frontend. The application requires authentication and authorization - so naturally I've got a few options:
1) Custom Login
2) Third Party via OAuth2
3) Both (what I would like to do)
My question is, how exactly would I go about implementing a custom authentication system with an Endpoints API? Since it's a RESTful service, I know that it's stateless. How exactly do I store session data? Do I have to send credentials with every API request (that seems tedious)?
Gah, could someone please point me in the right direction here? I'm not the most knowledgable person when it comes to authentication. THANK YOU!
There is a not well known nor documented feature in Google's cloud endpoints that allows you to use custom authenticators on api class level or api method level. This is also described / documented in a stackoverflow question.
There are a couple of questions here on stackoverflow for python like this, which uses cookies as far as i can see. I've not yet seen how to implement a custom authenticator like you can in Java.
As for how to store session data in a stateless service. The answer is simple: You don't. Every call to your api should contain all the information to process the request. So it's up to the client to maintain the session information and provide it when needed for an api call.
If by session data you mean stuff like the usual user data (name, address, etc) those are attached to your user (not the current session) so if you have a working authenticator you can simply request the user information from your database via the authenticated user.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
As I understand, App Engine Apps are OAuth 1 providers by default.
Is there a way to use OAuth2, e.g. with Google+ Sign-In or (mobile) chrome.identity API while still taking advantage of the GAE Users API and not having to implement a custom provider?
If not possible, what are the alternatives?
Can't say anything about what you refer to as "(mobile) chrome.identity API," but, inasmuch as I got to your question because of its google-chrome-app tag, I can answer for a Chrome App: Yes, it's possible to use the chrome.identity API to connect to an OAuth1 server (I've done it), but it's a lot of work, and you have to horse around with all of the OAuth1 handshaking. It's somewhat easier than trying to connect without chrome.identity, but not nearly as easy as connecting to an OAuth2 server, which is pretty much automatic.
Note that this is not a way of using OAuth2 to connect, which is what you literally asked. Rather, it is a way of using chrome.identity (for a Chrome App) to connect to an OAuth1 server.
Cloud Endpoints seem to be exactly the solution I need. They are not (yet?) a part of the official GAE for Go documentation, but can be found at Github.
Probably the best way to start is the examplary tictactoe app.
A quick test with the Google+ Sign-In button was successful (although with my probably wrong config it is performing multiple calls under the hood and some of them resulting in scoping errors).
I'm new with moodle in fact create java application using GWT and deployed it to appengine, really it was about keystroke authentication in which detect the unauthorized users from their typing behavior on keyboard, so I make a text area that takes some data form key and send it to the server side and make some comparisons with data in the app store, i found that it would be Awesome if i add that to module meanwhile this application is my graduation project so when i integrate with moodle it is useful point for me. My question is how can i integrate my application to moodle taking in consideration that i use the appstore .
I suggest you look into something called IMS LTI. Here is a good video introduction to it:
http://vimeo.com/14100773
Before IMS LTI in order to hook into Moodle you needed to write a Moodle plugin. But using IMS LTI you should be able to just enter in some details about your app, like the url and a shared key and using IMS LTI user data and responses should be passed between Moodle and your app. Future versions of the IMS LTI standard will also allow you to pass grading information.