Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SSL No Longer Trusted #2

Open
jpscharf opened this issue Dec 9, 2018 · 5 comments
Open

SSL No Longer Trusted #2

jpscharf opened this issue Dec 9, 2018 · 5 comments

Comments

@jpscharf
Copy link

jpscharf commented Dec 9, 2018

The SSL Certificate for https://api2-c.heartlandportico.com/SecureSubmit.v1/token/gp-1.0.2/globalpayments.js is no longer trusted by Google Chrome.

@jpscharf
Copy link
Author

@jpscharf
Copy link
Author

Still getting ssl warnings for iframe resources:

2018-12-10_15-56-39

@jpscharf jpscharf reopened this Dec 10, 2018
@charlie-s
Copy link

Related: globalpayments/node-sdk#2

@eric-vest
Copy link

Hi guys,

Yes, the cert on that domain needs to be updated but we're currently in a code freeze so it'll be at least until January before it's updated. Our current workaround is to use the old javascript library at https://api2.heartlandportico.com/SecureSubmit.v1/token/2.1/securesubmit.js. It doesn't use the api2-c for assets.

We'll close this issue once the cert is updated.

@charlie-s
Copy link

Thanks Eric! I didn't realize I could use the old securesubmit.js tokenization with the new SDK. That's good to know, I'll leave my old client-side code alone and migrate the back-end to use the GlobalPayments node-js library.

slogsdon pushed a commit to slogsdon/globalpayments-js that referenced this issue Feb 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants