Single Sign-On
This feature is available in our paid editions. Contact us here, and we'll be delighted to assist you!
Enforcing SSO
You can enforce SSO by specifying the domain. As part of the SSO configuration, you have the option to disable email and user login. This ensures that all authentication is routed through the designated SSO provider.
Supported SSO Providers
You can enable various SSO providers, including Google and GitHub, to integrate with your system by configuring SSO.
Google:
Go to the Developer Console
Create an OAuth2 App
Copy the Redirect URL from the Configure Screen into the Google App
Fill in the Client ID & Client Secret in Activepieces
Click Finish
GitHub:
Go to the GitHub Developer Settings
Create a new OAuth App
Fill in the App details and click Register a new application
Use the following Redirect URL from the Configure Screen
Fill in the Homepage URL with the URL of your application
Click Register application
Copy the Client ID and Client Secret and fill them in Activepieces
Click Finish
SAML with OKTA:
Go to the Okta Admin Portal and create a new app
Select SAML 2.0 as the Sign-on method
Fill in the App details and click Next
Use the following Single Sign-On URL from the Configure Screen
Fill in Audience URI (SP Entity ID) with 'Activepieces'
Add the following attributes (firstName, lastName, email)
Click Next and Finish
Go to the Sign On tab and click on View Setup Instructions
Copy the Identity Provider metadata and paste it in the Idp Metadata field
Copy the Signing Certificate and paste it in the Signing Key field
Click Save
SAML with JumpCloud:
Go to the JumpCloud Admin Portal and create a new app
Create SAML App
Copy the ACS URL from Activepieces and paste it in the ACS urls
Fill in Audience URI (SP Entity ID) with 'Activepieces'
Add the following attributes (firstName, lastName, email)
Include the HTTP-Redirect binding and export the metadata
JumpCloud does not provide the HTTP-Redirect binding by default. You need to tick this box.
Make sure you press Save and then Refresh the Page and Click on Export Metadata
Please Verify Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect" inside the xml.
After you export the metadata, paste it in the Idp Metadata field.
Copy the Certificate and paste it in the Signing Key field
Find the <ds:X509Certificate> element in the IDP metadata and copy its value. Paste it between these lines:
Make sure you Assigned the App to the User
Click Next and Finish