For our usecase/situation below; should we be using SuiteSignOn to make an outbound call or an inbound call?
Usecase:
We have a Netsuite webstore (SCA). People login and purchase medical tests from us. After customers have performed their medical test they can view their results in our external web application (PHP Laravel web app). We want to use 1 single sign on for both applications (NS webstore and Results web app). Ie, the user will use their SCA webstore account login details to login to both applications.
We expect customers to go to the Results web app and somehow login using their NetSuite user credentials. I assume NetSuite (SuiteSignOn) can embed a login form in a external web app?
So would the above usecase be considered a SuiteSignOn outbound call or SuiteSignOn inbound call?
Check into Google Auth. That is supposed to be released as soon as all of the 2017.1 upgrades are rolled out. That would allow you to use the same authentication credentials.
Related
We are using DocuSign API via demo account for signatures. We are using Authorization Code Grant workflow and are obtaining authorizations in our demo workflow. So real access tokens are being used.
But no API calls are being shown in our demo account API Dashboard.
But I can see via our monitoring tool we are hitting DocuSign. Plus the flow of the integration is all working properly.
Why are the calls not showing up? This is affecting our ability to proceed with app review process.
Notes
The model we're using is ISV
We use Authorization Code Grant workflow
We obtain user authorization for users outside of our account since we are an ISV
My question is similar to this one but we are using real access tokens.
The information in the dashboard may be outdate by 10-20 minutes as it takes some time for the process to get the API requests to the dashboard.
Please allow for a few minutes of delay and check the dashboard a bit later if you have new API calls you're trying to view in the dashboard.
Also, for ISVs, the portal only shows your own account. You must make the API calls from your own account that was used to create the IK. If you use a different account - it would not show in the developer dashboard.
Context
My team is working on an integration between a Web Application and DocuSign, where the user may send files to signing from our App to DocuSign (creating an envelope with the files).
In the envelope info inside our app, the user should have a link to be redirected to DocuSign (preferably to the Management page, but Home one is also acceptable).
Question
Since there isn't an endpoint on DocuSign eSignature API for getting a redirect URL (such as EnvelopeViews), and I couldn't find a document mentioning direct access to DocuSign eSignature (such as the one existing for DocuSign eSignature Admin), my question is...
Is there a known redirect URL to DocuSign eSignature that I could trust it won't change, so I can use it on our application?
I found out (looking at the authentication process) that the following URLs work for what I want...
https://appdemo.docusign.com/authentication?back=/home (Sandbox)
https://app.docusign.com/authentication?back=/home (Prod)
https://appdemo.docusign.com/authentication?back=/documents (Sandbox)
https://app.docusign.com/authentication?back=/documents (Prod)
But can I trust they won't change (since they aren't documented) and use them on my app?
For the management/web app for users, there's a way to do that with the API, you get back a URL that is pre-authenticated and is the recommended way to do that.
See here for code examples in different languages.
As for the administration/settings part, you would have to do it the way you indicated. We cannot guarantee this URL would never change, but it's not something that happen often if at all. However, users would have to log in (authenticate) when they are redirected unless in the same browser and already logged in.
I am new to Docusign and we have a requirement to integrate Docusign in our web app. I have gone through all the links for integrating docusign into a web app using REST Api calls. After thorough read and watching youtube videos, I came to know that we can integrate docusign in our web app through REST API calls but for the same additionally we need to develop our own UI to upload documents and send it to the recipient. But basically we are looking something where we can be reidrected to docusign from our webapp to perform all the operations of sending document for signing and once document is sent then I will be redirected back to our web app.
Kindly help with the above query and let me know if my understanding is correct for integration of docusign and for the same developing our own UI in our web app. Also please let me know if there is any alternative to fullfill the requirement of directly accessing docusign from our web app and performing all required operations of sending a document to recipient.
Thanks in advance!
So you want a button on your web app that says "Sign with DocuSign" and then what?
Most customers who want to send from their web app already have the documents controlled by their web app.
They:
authenticate the user with DocuSign (OAuth Authorization Code Grant)
Upload the document to DocuSign from their app.
Add tabs (signing fields) to the documents programmatically. (This is not hard and it saves the sender a lot of work.)
Upload the recipients (signers, copy-only recipients, etc)
And then tell DocuSign to send the envelope (the transaction).
Applications can also monitor the progress of the envelope through the signing process and programatically act on the signed documents.
The above is not hard to do and provides a good user experience.
You can also redirect the user of your application to DocuSign to accomplish any/all of the above manually. But the more the user does manually, the less convenient the integration will be for them.
If you want the manual experience, check out the EnvelopeViews::createSender method.
I need to implement a renewable subscriptions in my mobile application, with different plans, duration and prices (like Netflix is doing), that is valid on mobile but also in my desktop app.
I read many threads and I understood that the only way to know if the subscription is correctly renewed is to check it from the mobile app: this is a problem for me because if I bought a subscription in my mobile app and I stop using it, but I'm still using the desktop application, at the end of the subscription I will not know if the subscription was renewed (because the user never opened the mobile app) and so I'll block the user for log-in in the desktop app.
I also read that it's not possibile to use Stripe or Paypal to manage the payment in mobile app, because the store will block the application that is not using a proprietary purchase system to sell not-physical goods or services.
So, the question is: is there a way to make a recurring subscription and know if it's currently active or not and the total payed without open the mobile app? If not, how can I manage a recurring subscription both in mobile and desktop apps? May be I'll need to create an external web page using a webview and then use Stripe or Paypal?
Thanks.
Matteo
Font:
Renewalbe subscription on mobile
Implement Stripe in Xamarin
EDIT
Our purpose is to manage subscriptions on desktop application but give the mobile user the possibility to buy a plan also on mobile.
Is possible to use a web view or default mobile browser to redirect the user to desktop web page and buy from here, without have any problem when publish app on apple and play store.
I already have the HTML form method implemented but it's very slow encrypting the form data and redirecting to PayPal & an unencrypted form is not an option.
What I would ideally like to do is something similar to how Google Checkout Integration works. Connect to the PayPal web service, send across the contents of the basket and then redirect the user to paypal checkout.
It this possible using the PayPal API web service?
if you are in the UK then what you need is the Website Payments Pro Hosted Solution. Then you can use an API to connect to Paypal checkout. Call their Telesales team and they will point you to Website Payments Pro Hosted Solution.