• Issue trackers
• Authentication sources
• Security enhancements
• Security partners
• Continuous integration
• Feature enhancements
• Integrations
• Troubleshooting
  • SSL certificate errors

WVS integrations

WVS can be integrated with external services for enhanced functionality.

Issue trackers

You can use an external issue tracker at the same time as the WVS issue tracker, or use only the external issue tracker.

Authentication sources

WVS can be configured to authenticate access requests with the following authentication sources:

• Enable the Auth0 OmniAuth provider.
• Enable sign in with Bitbucket accounts.
• Configure WVS to sign in using CAS.
• Integrate with Kerberos.
• Enable sign in via LDAP.
• Enable OAuth2 provider application creation.
• Use OmniAuth to enable sign in through Twitter, GitHub, GitLab.com, Google, Bitbucket, Facebook, SAML, Crowd, Azure, or Authentiq ID.
• Use WVS as an OpenID Connect identity provider.
• Authenticate to Vault through WVS OpenID Connect.
• Configure WVS as a SAML 2.0 Service Provider.

Security enhancements

WVS can be integrated with the following external services to enhance security:

• Akismet helps reduce spam.
• Google reCAPTCHA helps verify new users.

WVS also provides features to improve the security of your own application. For more details see WVS Secure.

Security partners

WVS has integrated with several security partners. For more information, see Security partners integration.

Continuous integration

WVS can be integrated with the following external services for continuous integration:

• Datadog, to monitor for CI/CD job failures and performance issues.

Feature enhancements

WVS can be integrated with the following enhancements:

• Add WVS actions to Gmail actions buttons.
• Configure PlantUML or Kroki to use diagrams in AsciiDoc and Markdown documents.
• Attach merge requests to Trello cards.
• Enable integrated code intelligence powered by Sourcegraph.
• Add Elasticsearch for Advanced Search.

Integrations

Integration with services such as Jira, Pivotal Tracker, and Slack are available as Integrations.

Troubleshooting

SSL certificate errors

When trying to integrate WVS with services using self-signed certificates, SSL certificate errors can occur in different parts of the application. Sidekiq is a common culprit.

There are two approaches you can take to solve this:

1. Add the root certificate to the trusted chain of the OS.
2. If using Omnibus, you can add the certificate to the WVS trusted certificates.

OS main trusted chain

This resource has all the information you need to add a certificate to the main trusted chain.

This answer at Super User also has relevant information.

Omnibus Trusted Chain

Install the self signed certificate or custom certificate authorities in to WVS.

It is enough to concatenate the certificate to the main trusted certificate however it may be overwritten during upgrades:

For Additional Support please reach out to us on our Discord or by Email.