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

Certificate verify failed: unable to get local issuer #62

Open
bigdatanut opened this issue Sep 2, 2024 · 2 comments · May be fixed by #66
Open

Certificate verify failed: unable to get local issuer #62

bigdatanut opened this issue Sep 2, 2024 · 2 comments · May be fixed by #66

Comments

@bigdatanut
Copy link

bigdatanut commented Sep 2, 2024

Hi,

we try to configure the Splunk input to monitor an on Prem bitwarden installation with self signed certificates.
Is there an option I can use in Splunk configs to point it to the CA?

2024-09-02 16_25_18-Zoom Meeting

@bitwarden-bot
Copy link

Thank you for your report! We've added this to our internal board for review.
ID: PM-11586

@bigdatanut bigdatanut changed the title Certificate verify fasiled: unable to get local issuer Certificate verify failed: unable to get local issuer Sep 2, 2024
@Adedamola-Aina
Copy link
Member

Hi @bigdatanut

I am unable to reproduce this issue.

We use GitHub issues as a place to track bugs and other development related issues. If your issue persists, please write us back using our “Contact support” form located on our Help Center (https://bitwarden.com/help/).

You can include a link to this issue in the message content.

Alternatively, you can also search for an answer in our help documentation or get help from other Bitwarden users on our community forums (https://community.bitwarden.com/c/support/).

The issue here will be closed.
Thanks!

@mzieniukbw mzieniukbw linked a pull request Sep 22, 2024 that will close this issue
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

Successfully merging a pull request may close this issue.

3 participants