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.

Sign up for GitHub

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

Jump to bottom

Faraday::SSLError #125

Open
bragovo opened this issue May 16, 2018 · 4 comments
Open

Faraday::SSLError #125

bragovo opened this issue May 16, 2018 · 4 comments
Labels
bug Something isn't working help wanted Community assistance requested to be implemented in v1 This issue or pull request will be resolved in the v1 rework, but has not yet been completed.

Comments

@bragovo
Copy link

bragovo commented May 16, 2018 •
edited
Loading

On every Ubuntu systems with rbenv and ruby 2.5.0 not working auth through VK provider. On Mac everything fine and FB provider work fine too. Is that problem with sorcery or faraday or Ubuntu?

Faraday::SSLError (SSL_connect returned=1 errno=0 state=error: certificate verify failed (certificate has expired)):

VK and FB auth in devise gem working fine.
@bragovo
Copy link
Author

bragovo commented May 16, 2018 •
edited
Loading

Set config.ca_file = '/usr/lib/ssl/certs/ca-certificates.crt' and now auth fine. Maybe default ca_file outdated?

@Ch4s3
Copy link
Contributor

Ch4s3 commented Jul 9, 2018

@bragovo could be? Sorry I don't know too much about this and I've never used the FB provider. could you check with the Faraday folks?

@anaumov anaumov mentioned this issue Jul 25, 2019
Open
@joshbuker
Copy link
Member

The pr #200 addresses this, but is blocked by validation that the new CA is correct / safe.

@joshbuker joshbuker added bug Something isn't working help wanted Community assistance requested labels Dec 19, 2019
@joshbuker joshbuker added the to be implemented in v1 This issue or pull request will be resolved in the v1 rework, but has not yet been completed. label Jun 5, 2021
@joshbuker
Copy link
Member

The ideal resolution for the whole CA issue will be offloading that responsibility to Omniauth, imo.

Assuming there are no issues switching to Omniauth, this will be fixed in v1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working help wanted Community assistance requested to be implemented in v1 This issue or pull request will be resolved in the v1 rework, but has not yet been completed.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@bragovo @joshbuker @Ch4s3