-
Notifications
You must be signed in to change notification settings - Fork 699
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
SSLHandshakeException occurs during call to authenticate in Google Drive API #1821
Comments
We are running into an issue very similar to this. Our java returns the same error. In our case, the issue is that when the code is run on the server, the initial handshake request to the google server does not include the SNI in the request.
This is the packet response we get when montoring with Wireshark
Running the same code locally does not have the same issue. The SNI is passed as expected. Not sure if this is a bug in the library or some misconfiguration in our server.
Java Info:
Any suggestions or recommendations would be greatly appreciated! Our google integrations are dead in the water until we can find a solution for this... |
Im using the Google Drive API quick start java project which includes google-api-java-client jar library.
When i perform the TokenRequest Authorization call in Google Drive i receive SSLHandshakeException.
Few forums says to import the certificate to java trusted certificates as a generic solution for SSLHandshakeException.
But im not sure how to get a certificate in this case. i mean which url is needed to be launched in a web browser to get the certificate to add in Java trusted certificates. Please help to fix this issue.
Environment details
Java(TM) SE Runtime Environment (build 1.8.0_181-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode)
External references:
https://stackoverflow.com/questions/39842033/java-quickstart-for-google-sheets-api-crashes-with-pkix-path-building-failed
https://developers.google.com/drive/api/v3/quickstart/java
Stacktrace
Thanks!
The text was updated successfully, but these errors were encountered: