URL: https://pilot-payflowpro.paypal.com
Until 12 April 2017 I had no problem but as of 13 April I failed to create a secure token.
There were no changes to the code nor to the account settings (no change in password, no "allowed IP addresses, ...").
The same code using paypal production accounts still works.
Apart from the TLS 1.2 and HTTP/1.1 upgrade I don't know about any changes on the PayPal server side.
Anyone having similar problems?
After some more digging I decided to contact PayPal technical support and I eventually (after 5 weeks) got this reply:
"There was a batch a few months ago that disabled Test accounts that hadn't been in use for a while.
They can be re-enabled only from our side...
Apologies for the inconveniences."
They kindly re-enabled our accounts and all was fine again.
Related
I have an existing Xero app that's worked well for over a year that uses OAuth2 to connect a small number of organisations to one of three Web Apps: developer, sandbox, and production. Sandbox and production are working well. However, yesterday I started to create a new instance of the developer app and am unable to complete the first step. My app calls the following URL:
https://login.xero.com/identity/connect/authorize?response_type=code&client_id=069BFC79B7REDACTED&redirect_uri=https%3A%2F%2Fdev.addressredacted.ngrok.io%2Fcotrustee%2Fxero&scope=offline_access+accounting.transactions+accounting.settings+accounting.journals.read
This URL has the same form that has worked for over a year, just with a new client_id, but now I keep getting this error:
Access Denied
You don't have permission to access "http://authorize.xero.com/?" on this server.
Reference #18.d2fdda17.1671639885.53ec38b
I expect to be redirected to a Xero login page instead.
From the Ref# that you received, it looks like it has hit the Akamai WAF. Unfortunately the code has expired (it only has a lifetime of 24 hours) thus we are unable to check why it was blocked.
Can you contact Xero API Support - api at xero dot com - with a newer reference so we can further investigate?
In a few days' time my SSL certificate expires on PayPal. Normally I would go to Account Settings > Website Payments > Encrypted Payment Settings to upload a new certificate. However, attempting to do so since several days yields a "That page doesn't exist" error. From reading other forums it would seem I am not alone. PayPal Cust Support know nothing of this, and I am still waiting on a response from PayPal Merchant Tech Support (MTS). However, time is critical and in a few days' time I will be completely dead in the water if I cannot upload a new cert. I've heard an unconfirmed rumour that Encrypted Payment Settings is no longer supported, although I've had no official comms. Can anyone confirm?
Needless to say if this is something PP are quietly retiring under the hood with no warning, thereby knowingly and suddenly leaving people without a working eCommerce solution then...
Date of Post is 30 Sep 2021 .Postman is not giving any response when SSL is enabled while hitting a api, but showing response with disable SSL. But my question is, the TLS "authorizationError" ="CERT_HAS_EXPIRED" but "validTo:" "Dec 15 02:30:21 2021 GMT" still have date.Means still the certificate is in valid date.Thanks for the help
You use let's encrypt. Normally the certificate would have expired today, but the have an extended period of live.
Postman has not updated our internal certificate store.
I faced this error. If you are completely sure your SSL is valid, then
Update Postman to the latest version and restart Postman
Your request should work after that. If this helped you, an upvote would be appreciated
Postman didn't update their internal Let's Encrypt certificate in time to handle the expiry of the previous one.
They acknowledged it on GitHub and released a patch on October 1st, so updating your Postman client should correct the error.
I'm having the error below since January 1st, 2018 when trying to login in my system with Linkedin OAuth2:
500 Server Error: Internal Server Error for url: https://api.linkedin.com/v1/people/~:(email-address,first-name,headline,id,last-name,picture-url,positions,public-profile-url)?format=json
For three days our system was having that error then on the 4th day I just removed Linkedin Login option on our website.
Today, January 11, I've tested again with the hope to enable Linkedin Login again, and the error is still there.
I've seen a similar question and the comments give the idea that it was solved but it wasn't yet.
I don't have reputation to comment on that question, that is why I'm asking here.
Some of you know how to contact Linkedin guys to solve this problem?
It's a problem in their servers.
So for a while I've been relying on the PLAIN support for logging into Google's IMAP server in my email client. Recently they started blocking that and return an error (despite listing it as a supported authentication method).
For instance take this example:
Connected to 'imap.gmail.com:993' using SSL
A0001 CAPABILITY
* OK Gimap ready for requests from ##.##.##.## cd6mb38777249ieb
* CAPABILITY IMAP4rev1 UNSELECT IDLE NAMESPACE QUOTA ID XLIST CHILDREN X-GM-EXT-1 XYZZY SASL-IR AUTH=XOAUTH2 AUTH=PLAIN AUTH=PLAIN-CLIENTTOKEN AUTH=XOAUTH
A0001 OK Thats all she wrote! cd6mb38777249ieb
A0002 AUTHENTICATE PLAIN
+
####################################
* NO [WEBALERT https://accounts.google.com/ContinueSignIn?sarp=1&scc=1&plt=AKgnsbszktZSU6iVmh...snip....] Web login required.
A0002 NO [ALERT] Please log in via your web browser: http://support.google.com/mail/accounts/bin/answer.py?answer=78754 (Failure)
SSL connection closed.
ScribeImap_Thread.cpp:647 - Connect to imap.gmail.com:993 failed.
I've tried opening the "https://accounts.google.com/ContinueSignIn..." URL in my browser:
And I get redirected to https://myaccount.google.com/ but the next login attempt fails as well. So it doesn't seem to change the authentication at all.
Is the PLAIN authentication just blocked completely or am I doing it wrong?
Alternatively is there a authentication method that works and DOESN'T need a browser component to log in? (XOAUTH2 seems to need a web login as well)
It's pretty official:
http://googledevelopers.blogspot.com.au/2015/04/a-final-farewell-to-clientlogin-oauth.html
They have shut off PLAIN login completely and it's not coming back.
So there are two options:
Turn on "less secure apps".
Implement OAUTH2.
I've decided to implement OAUTH2 support (which isn't too far off working actually). Initially I thought I would need an embedded browser component in my app, but it turns out that I can launch the system browser and the user can copy the token across in a some what manual process.
Interestingly for those working on OAUTH2 support in their software, Google have setup a playground to see the whole process in practice:
https://developers.google.com/oauthplayground/
I see that this is an old post, but after fighting with Outlook for over a year to get my mail, I FINALLY got it working again.
The first thing I had to do was log into my my Gmail account and turn off the button labeled "Less secure apps" as Outlook is in that category.
Go to the "Less secure apps" section in My Account.
Next to "Access for less secure apps," selectTurn on. (Note to Google Apps users: This setting is hidden if your administrator has locked less secure app account access.)
And if you have 2-step verification on (as I did), it will still make Outlook fail. So the next thing you have to do is create an app password which will generate a password for you, and you use that in Outlook for it to sync correctly.
Visit your App password page. You may be asked to sign in to your Google Account.
At the bottom, click Select app and choose the app you’re using.
Click Select device and choose the device you’re using.
Since Outlook will not be listed, select Other and type in Outlook for future reference.
Select Generate.
Follow the instructions to enter the App password (the 16 character code in the yellow bar) on your device.
Select Done.
Copy the password that was generated.
Open Outlook and paste the password in the Password section. DO NOT use your regular password.
Your mail will sync without anymore issues. (Hopefully)
Once you are finished, you won’t see that App password code again. However, you will see a list of apps and devices you’ve created App passwords for.
I hope this helps everyone who is having an issue. And I hope these directions are easy to follow! Good luck everyone! :-)