Congratulations, you've successfully installed FOSSA! Here are some common follow-up tasks once your installation has succeeded. All of these steps are optional, although we recommend reading through this document to ensure you haven't missed anything in your installation.
Some of these customizations may require changing your Helm values. To apply those changed values to your cluster, see Updating Helm values.
FOSSA supports integrations with many third-party tools and services.
To configure Google Workspace SSO, add the client ID and client secret of your Google Workspace OAuth application in your Helm values:
google: clientId: 0123456789abcdef.apps.googleusercontent.com clientSecret: fakeSecret0123456789
To use Quick Import, you'll need to integrate FOSSA with the SCM provider that hosts your source code repositories.
To configure SCM integrations such as GitHub, GitLab, and BitBucket, you'll need to add a client ID and client Secret for your SCM's OAuth application in your Helm values:
# See your values file template for examples for other service providers. github: clientId: 0123456789abcdef clientSecret: fakeSecret000000000000000
SCM integrations can also be used for SSO. For example, configuring the GitHub integration also allows your users to sign in to FOSSA with GitHub. If you don't want users to sign in with these options, you can restrict the sign-in options that your organization permits in the application's UI under Organization Settings.
Each SCM integration has different fields specific to the SCM vendor. For details for each vendor, see the reference documentation comments in
FOSSA can send notifications to a Slack channel. This requires creating an OAuth app on Slack, and providing the client id and secret in your Helm values:
slack: clientId: abcdef clientSecret: abcdef
Once FOSSA is installed, you can configure SAML and LDAP in the Organization Settings page in the application's UI. For more details, see our product documentation at docs.fossa.com/docs/single-sign-on.
As a FOSSA administrator, you might sometimes want to send informative messages to all FOSSA users. On-premises installations of FOSSA support setting instance-wide notification banners:
You can set these banners in your organization settings:
Updated about 1 month ago