Skip to main content

SSO - high level HOW-TO

What is it about?

Long story short - SSO is for easier authentication process. Instead of maintening a local user database on the Wordbee platform it’s possible to use the centralized authentication system which you have in place. Here’s the high level diagram about how SSO authentication works. In our case, Wordbee platform is a Service Provider (SP), your centralized user database (Windows AD, Azure AD etc) is a Identity Provider (IdP).

As soon as SSO module enabled for your platform you will see an additional option for authentication on the login page

IMPORTANT NOTE: it’s only possible to integrate ONE IdP (Identity Provider) per platform, so you will not be able to use multiple authentication providers for the same Wordbee platform.


Easier user database managing and authentication

Sometimes you would need to create Wordbee platform local users and use SSO just for authentication and mapping to those existing accounts. But Wordbee SSO module can handle automatic user creation for you and then just take care about proper mapping.

Users passwords are secured

Users passwords are never stored on the Wordbee side. Wordbee SSO will always ask your IdP before allow user to be logged in.


Here’s two main iterations to be completed in order to enable SSO for your Wordbee platform:

  • Create SAML instance config on your IdP portal using an information from Wordbee SAML metadata xml template.

<?xml version="1.0"?> 
<md:EntityDescriptor xmlns:md="urn:oasis:names:tc:SAML:2.0:metadata" entityID="wordbeesso">
  <md:SPSSODescriptor AuthnRequestsSigned="true" WantAssertionsSigned="true" protocolSupportEnumeration="urn:oasis:names:tc:SAML:2.0:protocol">
    <md:KeyDescriptor use="encryption">
      <ds:KeyInfo xmlns:ds="">
    <md:SingleLogoutService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect" Location="https://{{PLATFORM_DOMAIN}}/a/{{PLATFORM_NAME}}/Access/Logout.aspx"/>
    <md:AssertionConsumerService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST" Location="https://{{PLATFORM_DOMAIN}}/a/{{PLATFORM_NAME}}/Access/LoginFromExternal.aspx" index="1"/>

Basically you need the entityID, SSO Login/Logout URLs and public certificate for SAML response encryption. Please just replace {{PLATFORM_DOMAIN}} and {{PLATFORM_NAME}} with your data (ask Wordbee support team if you’re not sure about a proper naming).

  • Get and share with Wordbee IT team the needed SAML settings

IDP name

SSO url

IDP certificate (signing)

Want response signed Yes/No

Want assertion signed Yes/No

Want assertion encrypted Yes/No

If you want to apply something special for user mapping and authorization it should be discussed separately with Wordbee DevOps team and then applied and tested.

If something went wrong…

Call Wordbee Support team or mail us on

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.