Currently i am adding feature to connect razorpay merchants on my site using https://razorpay.com/docs/oauth/authorize/#authorization-url
and generating url to redirect merchants for login and permission on below URL
https://auth.razorpay.com/authorize?client_id={client_id}&response_type=code&redirect_uri=http://localhost:3000/admin-home&scope=read_only&state=NOBYtv8r6c75ex6WZ
Note: client id is generated and downloaded from https://dashboard.razorpay.com/app/keys page
but when above URL is opening in new window it gives below error
can someone please help me to solve this problem?
Please check whether you have whitelisted the redirect_uri, as per the instructions.
It is highly possible that there are validation placed based on the whitelisting which is preventing you request from going through.
It is explained in Step 1 on the same documentation which you have gone through.
Related
We have a web application written in React that integrates with Stripe to take payments.
When the user accesses the Apply Pay option, the popup immediately closes before they can complete the transaction.
The domain has been added to the Apple Pay settings on Stripe
There are no errors or logs in the javascript console to indicate an issue.
This is using Stripe Connect
The same page works perfectly on Google Pay
The page in question is publicly accessible here: https://whitecobalt.rendr.co.uk/pay?key=0tRvBe7q4E10230
I have recorded a screen-share video of the issue, which can be viewed here:
Has anyone else experienced this or is able to point us in the right direction, we've tried everything, and we're a bit stumped!
Thanks in advance!
That usually means you didn't register the domain correctly for Apple Pay with Stripe.
On that page you are using Connect, you are trying to initialise stripe.js with the account acct_1M1B1IQ0dY0splyg.
So in that case you need to register the exact domain whitecobalt.rendr.co.uk on the connected account by making the /v1/apple_pay/domains API call described at https://stripe.com/docs/stripe-js/elements/payment-request-button?client=html#html-js-using-with-connect , using the livemode secret key of your platform account and that domain name/account ID as params.
Thank you - I have it working now.
It seems when you're working with Stripe Connect you need the domain in both the master Stripe account and the connected Stripe Account - then it works!
I've just been started integrating assistant to smarthome project that i'm working on. And I've initially experimenting the assistant by implementing account linking flow and sync intent. I tested the account linking by testing with the google developer tool for oauth flow and confirmed it worked. Whereas, in the smarthome app, upon account linking, as soon as it completes the account linking flow I keep receiving an error message stating "Couldn't update your settings, Check your connection". Didn't find much clue with the logs for troubleshoot. And also, the solutions they were on the other posts does not seem to be working out for me as well. Would appreciate if anyone could help resolve this.
Also, I'd like to know the place where I can find the fulfillment URL that needs to be entered when creating the smarthome action. I've been using firebase to deploy my cloud functions. Moreover, I suspect weather the fulfillment URL I entered that was provided by codelabs sample were invalid thus assisant unable reach the fulfillment.
Your fulfillment URLs are the functions that you've created. For Firebase, there's a specific pattern that you can follow. If you visit your Firebase console, in the functions section, you'll see the full URL which you can copy and paste into the Fulfillment URL input.
In my example, I have a cloud function named "about_info" with the pattern https://us-central1.PROJECT_ID.cloudfunctions.net/FUNCTION_NAME. So you can use a similar scheme to identify what your function names will be.
We have a React application protected by a separate Identity Server site. When unauthenticated, the user is redirected to the login page within Identity Server and then on successful login they are then redirected to a callback URL within the React application.
I'm trying to automate this process as much as possible to improve the speed and reliability of our Cypress.io tests so that we don't need to login via the UI each time - allowing the tests to be atomic and free of unnecessary complexity.
What would be the best way to achieve this?
I've followed the examples the Cypress team give around logging in, but haven't been able to get it close to optimal:
https://github.com/cypress-io/cypress-example-recipes/tree/master/examples/logging-in__single-sign-on
The closest I've come so far is by following this Auth0 article, but fell short of populating the id_token, nonce and state values to pass to the callback URL:
https://auth0.com/blog/end-to-end-testing-with-cypress-and-auth0/
Any direction greatly appreciated.
I was able to get around this by hitting the /connect/token endpoint of the Identity Server:
POST /connect/token
client_id=client1&
client_secret=secret&
grant_type=password&
username=username&
password=password&
scope=openid profile <client_scope>
And then used the response to add an item into session storage:
window.sessionStorage.setItem("oidc:<auth_url>:<client_id>", JSON.stringify(response));
I am phone-gap developer. I make a application for getting like and comment via post image caption on Facebook. So we are using a plugin of iOS and android for the same but i am not getting any post-id in return after sharing the image through default share dialog in both.
Plugin Link : https://github.com/jeduan/cordova-plugin-facebook4
Use Case in android :-
1- We are getting post-id when Facebook application is not installed in device.
2- But we are unable to get the post-id when Facebook application is installed in the device.
Use Case in iPhone :-
1- We don't get any response after sharing images in iPhone device.
2- But getting response (post-id) when share through simulator.
Please help me with proper solution. It would be great if you join us in team-viewer to solve our problem.
Thanks in advance.
The only way to get the post id is to authorize users with the publish_actions permission - you would also need the user_posts permission to get access to the new post in order to get the likes/comments. According to your comments, you want to pay users for those - which is not allowed and Facebook will never approve the required permission in the neccessary login review process.
In other words: It is not allowed and not possible.
Ive been advised by Docusign to post here.
I have 4 clients who I've installed the Docusign for Salesforce App for. I've followed the installation instructions and every time I end up with the same error. When it comes to entering my Salesforce credentials it says they are wrong or I have not added the trusted network. I know the credentials are correct and I have entered the trusted network. I've tried various things like using security token in the password, configuring at the docusign end. Nothing works, Docusign don't know what the issue is, I've also raised a case with Salesforce and they can't help. I can't understand why an App on the app exchange can't get passed configuration and noone can help! Hopefully someone here can help. Thanks
The DocuSignAPI tag on Stack Overflow is used for api development and integration questions normally, however I will try to address your issue...
First off, if you could update your question with a screenshot of the error and screen you are on when you receive the error that would help isolate the issue.
With that in mind, what screen are you on? Are you on the screen that's titled "Connect DocuSign to Salesforce"? Even though you've mentioned I just want to double check that you are entering your Salesforce user credentials and not your DocuSign credentials.
Next, what environment are you selecting? And what type of DocuSign account do you have? You need to make sure that you are pointing to an environment where you have an existing account. For instance, if you have a DocuSign demo account but you are pointing to Production during the install, you might get that error.