I was develop and application, which can produce number of associated table if for a user and when user select appropriate client he can view report based on user id, password and table id.
Now, google change authentication process and introduce Auth2.x process to authenticate a user.
Is there any body who can help me regarding this problem, this will be a great help.
I am a .net developer so any help in dotnet will be much appreciated.
Thanks a lot in advance.
Take a look at this link https://developers.google.com/analytics/resources/articles/gdata-migration-guide. Look at section "Create a Project in the Google APIs Console" it will walk you through the whole process. This is what I used and it helped.
Related
I've developed an application that works through Google's GSuite using OAuth2. The app is working fine and is part of the GSuite account that was set up to allow testing while developing it (which is the owning account of the app in the Developer Console). However, I now want to give the app to another GSuite company but can't see how to get them to add it?
The application has been submitted for review with Google to get it added via the Marketplace but we're keen to get the second company using it ASAP. I've had a look through the Google docs but couldn't find anything that appeared relevant and even tried to see if I could find an existing question on here. If anyone can point me in the right direction that would be much appreciated!
Cheers
You won't be able to give it to another company until it's published, so if the review is taking linger than expected, your best is to contact Google GSuite support
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
I'm struggling to get the best choice for me in terms of kind of license I need. I just want to connect my website using chatter through OAuth2 as well as I have been developing a canvas app. Everything has been done with my developer account in Salesforce but I have been wondering if I need to purchase any kind of salesforce license to use it. Even I have been wondering if I need a new license to upload my canvas app to salesforce appexchange.
I will be really grateful if someone could tell me something about it because I don't really know what I should do due to salesforce licenses are expensive.
Thank you so much
Diego
First thing I would suggest you to do is create a Partnerforce account here if you are planning to sell your app on appexchange. After that, log a case on partnerforce asking them how to go about it. They are helpful people and should be able answer your questions well.
To list the app on Salesforce you will have to follow certain steps:
1) Firstly join the DeveloperForce free.
2) Signup for Salesforce Partnership
3) Now through APO Create a Test Org and select Partner Developer Org
4) Through AppExchange you can easily publish your First app after packaging it.
5) You will also have to go through Security Review before publishing the app. After the security review you can easily be able to view your package on AppExchange.
To get live on AppExchange just these steps are to be followed or you can also take the help of any experienced or existing Salesforce partner to get complete information abput listing your app on AppExchange. They can guide and help you throughout the procedure and to pass the Security review as well of Salesforce. A well known Salesforce partner is Janbask, who provide Salesforce implementation service and can provide you assistance and consultation as well. As they are Salesforce partner so know how to complete the process.
Apart from this you can try any Salesforce learning or training institute, if you are in your learning stage who can provide you complete detail and solution of your problem. You can easily Integrate Salesforce and be able to view your app on AppExchange.
I have experience developing in MS Access and some Java programming with Adobe Flash Builder.
I would like to create a website where a user can sign in and share and post things similar to Facebook, i.e a social network. I would like to know what is the best program for developing a website (for someone who does not come from an html background) and what is the best database to support this type of website i.e ( Oracle, Mysql ... )
If you have any advice or input please let me know. All advice is effective for me.
A user based website should be implemented both at the front end and the back-end of the application. Components such as username, login, and other information should be obtained upon sign in in order to implement a user-based website. The back end of the site should be on a production server that consists of both php and a sql server system of some sort.
Summary of the question:
I would like to create a CakePHP based registration and login system offering multiple different gateways such as OpenID, Facebook, Twitter, and so forth. I would like the system to allow a user to associate multiple forms of identification with their account.
After much searching, I am turning up a blank on anything that would allow more than one method of authorization. Cake's authorization system does complicate the matter, so using a tutorial for general PHP is not really effective. Does anyone have a solution, or somewhere I can start from?
Example:
To give a simple example, looking at the StackExchange network: you can login/register using a stack exchange account, Google, Yahoo, Facebook, or OpenID. Once logged in, you can add more of these methods to your account so that you are recognized a multitude of ways. I realize StackExchange probably isn't written in Cake, but it serves as an example.
Thank you!
Original Question
Here's the scoop: I'd like to integrate a simple registration/login system for each of the main services that offer oauth/openid in CakePHP.
Basically, I'd like my users to be able to register the old fashion way (including validation e-mail) or using an existing service to verify themselves. I'd like them to be able to login afterwards using that service, or with a username and password.
Now, I have found extremely in depth plugins for full facebook integration and the like, but the bottom line is that I want to just use this for registration and login at this point, and I would like the experience to be the same regardless of which service they choose (plus, I'd like to understand how it works... because this is all about learning CakePHP after all).
I'd also like them to be able to link other services once the account is created if they so desire. In a nut shell, they're account should be able to be linked to any number of login services, or none at all.
How on earth do I go about this?
Thank you,
James
Looks like there is now a third-party library available using Opauth as detailed on this bakery thread
Here is the CakePHP version's github page:
https://github.com/uzyn/cakephp-opauth
Great question - our CakePHP development studio may be looking at this in the coming months also. I suspect you'll have more luck researching this as a general PHP question and then how you can port that solution into Cake. Definitely post back with anything you discover.
You might find this thread a helpful starting point, although it was posted back in 2010:
Best way to implement Single-Sign-On with all major providers?