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).
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 1 year ago.
Improve this question
NextJS has a solution to build your own API and have it handle things like authentication and making database requests.
If I'm using using Vercel to host my app, is there a real reason (other than cost) to use Firebase Cloud Functions separate from NextJS, or do they work the same?
Will it be easier to have all my server side things on NextJS and Vercel rather than have it on Firebase Cloud Functions?
There are a few things to consider when deciding between Firebase Cloud Functions and Next.js API routes.
Reasons to use Cloud Functions
Trigger on database changes
If a document is added, you can use a Firebase Cloud Function to do something with the data. Next.JS will not be automatically triggered.
Integration with Google Cloud
If you want tight integration with Google Cloud, you may wish to just stick with Firebase. Other than error logging, I can't think of any specific reasons why this would be a deciding factor, but it may be a factor for your use case.
You need more then a REST API
There are multiple types of Firebase functions. Callable, HTTPs, triggered, etc. If all you need are HTTPs functions, you can probably just use Next.js functions. But anything more isn't possible with Next.js.
Deploy functions independently
With Next.js, to update a function, you need to redeploy the entire site again. With Firebase functions, you can deploy one function at a time.
Reasons to use Next.js API functions
If on Vercel, they're basically free
Since the entire Next.js app is broken down into serverless functions, Vercel essentially doesn't place [its normal limits on Next.js API function calls][1]. I haven't had a project where the price was really a factor since Firebase functions are so cheap, but perhaps it's something for you to consider.
Simpler development
With Firebase Functions, you also need to setup and use the emulators when in development. Next.js API functions are, well, apart of Next.js and work automatically in development.
My choice? If the project can work with only Next.js API routes, I stick with that. IF not, I code everything in Firebase Cloud Functions. It just keeps things simpler that way.
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
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
I am thinking about creating an app using AngularJS, NodeJS , and SpringBoot WebServices.
Should I use NodeJS(Express) web services between AngularJS app and SpringBoot WebServices ? If yes or no, please tell why.
Look forward to hearing your opinions !
AngularJS -> NodeJS(Express) -> SpringBoot WebServices -> DB
Note that Javascript is NOT Java.
It is rather strange to build your backend through two different kind of technologies. I would say you either go with just NodeJS (Javascript) or only SpringBoot (Java).
Building a server using NodeJS's express module as your middleware and then SpringBoot as your web service simply doesn't make sense to me... Unless you are saying you are intending to build a NodeJS application to act as a proxy server to talk to another server that serves resources written in Java. Otherwise I don't see why you need to setup a NodeJS application and another Spring application on the same server to work together serving certain resources.
Even if the combination make sense, using the 2 different technologies would mean that your server application will be running 2 different processes;
a Java process for your springboot application
a Node process for your nodeJS running express
Since each process will have its own memory space, this means that for both processes to communicate they will have to use the TCP/IP networking stack (http request). Where this and many other complicated considerations could be avoided, if you just go fully with 1 of the techs.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
I am developing a web, iOS and Android app simultaneously.
I have setted up phalcon that connects to Cassandra database and it is used for an API gateway.
All requests are HTTP and nothing connects directly to Cassandra everything is filtered in Phalcon developed app.
Now, I have to consider the login behind the dashboard and the way to develop a fast and scalable user interface.
What to choose for better development and of course safety; Laravel or AngularJs?
AngularJS is a front end framework and Laravel is a backend framework, comparing them is like comparing apples to bicycles.
Seriously though:
Authentication and database access are fundamentally backend procedures. The framework used to manage the business logic around this are frameworks that run on the server itself, and typically expose a web server and API calls. PHP is one of those languages and is not run in the browser (client) or on any native mobile system (ios/android). Laravel is a framework built around server side PHP to help with these procedures.
The client is the actual browser or mobile phone that is connecting to the back end services through http requests and manages the user experience and UI. AngularJS is a front end javascript framework built for the browser.
If this is news to you, you need to learn a lot before you dig into laravel and angular. Good luck!
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.