Stuck on getting access token for Credit Card (paypal) - api

I am working on an application which uses Paypal REST API for payments.
I have a client ID & secret but when I try to fetch the access token I get the following error message-
Invalid HTTP response The underlying connection was closed: An unexpected error occurred on a send
What could be the problem? please suggest.
Thanks in advance

Fixed this. The version of Newtonsoft.JSON was not compatible with paypal rest API & the webconfig on server was not updated with the package includes.

Related

Flutter Google Sign In Couchbase Authentication Code Flow

As we are migrating our app from Firebase to Couchbase, we also need to change the authentication part. We are using the google_sign_in package and would like to continue using it to have the native Google Sign In popup. Using the package we can get a serverAuthCode, which from my understanding we can then send to the _oidc_callback endpoint of Couchbase Sync Gateway. First I had to set disable_callback_state to true in the Sync Gateway configuration ("DisableCallbackState determines whether or not to maintain state between the /_oidc and /_oidc_callback endpoints."). However, when I now send the serverAuthCode to the _oidc_callback endpoint, I get the following error with status code 500:
body: {"error": "Internal Server Error", "reason": "Failed to exchange token: oauth2: cannot fetch token: 400 Bad Request\nResponse: {\n \"error\": \"invalid_grant\",\n \"error_description\": \"Bad Request\"\n}"}
I assume it is because the login was done using the package and not through the browser with a redirect to the app afterwards. Now I have no idea how to do this correctly though, that I sign in with the google_sign_in package and then use the code to get the tokens from the Sync Gateway. I can't find any helpful information for this problem.
I would be very happy if someone could help me, possibly in a call. Maybe this way something like this can be solved faster.

Error using REST API: "error_description": "AADSTS7000215: Invalid client secret is provided.\r\nTrace ID:

I'm trying to use the REST APIs to delete Assets in Purview but I keep this error:
"error_description": "AADSTS7000215: Invalid client secret is provided.\r\nTrace ID:
I have an App Registration that is assigned both the Owner and Purview Data Curator of my Purview Account.
When I enter the values of the App Registration along with it's client secrets (screenshot 1) into Postman I get an invalid client error (screenshot 2)
Screenshot 1
Screenshot 2
Any suggestions as to what I'm doing wrong? Thanks in advance?
Yes, indeed. It was the Secret Value.
Glad this was such a simple fix!

data accessing from Rally

I am trying to access rally data with API key,username and password but getting "HTTP ERROR 401 Problem accessing Reason: Full authentication is required to access this resource Powered by Jetty" issue.
I am using Node Version 10.18,
Can anyone help me in this.

Box API token request enterprise configuration issue

I am making a call to https://api.box.com/oauth2/token to get a token for a user.
I get a 400 with the following error:
Cannot obtain token based on the enterprise configuration for your app
I don't see this error message defined anywhere. Any ideas what I'm doing wrong?
The issue here was that I was requesting a token for a non app user and my application was configured to allow access to app users only.

Getting Invalid Authsub Token Error 403

I am trying to authenticate my application using Blogger API but when user grant access to the application and blogger api return the token and the token i use to exchange the by sending the request on https://www.google.com/accounts/AuthSubSessionToken it return an error called Error 403 Invalid AuthSub Token. Kindly help me in this regard to debug the problem and solve it. Thanks in Advance
after doing some experiment, here it is some advice :
change secure to zero
https://www.google.com/accounts/AuthSubRequest?scope=https://gdata.youtube.com&session=1&secure=0&next=http://www.example.com
make sure you are requesting from http for and request in http again in future
https://www.google.com/accounts/AuthSubRequest?scope=http://gdata.youtube.com&session=1&secure=0&next=http://www.example.com
it's worked like a charm for me...