On Premise and Private Cloud Customizations

Note

Applies to: On-premise and private Azure Cloud scenarios (not for SAAS www.theidentityhub.com)

If you have a private instance of The Identity Hub installed a lot of customization can be performed.

Customizing the look and feel

The look and feel of The Identity Hub can be completely customized to meet your organisation's look and feel and/or brand. Using simple CSS and HTML skills you can modify any page to your liking without impacting the possibility to upgrade to a newer version.

We also support translation of pages if the language you want to use is not available out-of-the-box.

For more information see Customizing the look and feel

Custom Account Providers

Although The Identity Hub supports many out-of-the-box Account Providers, you might need one that is not available because:

  • You want to support a proprietary authentication method
  • You want to support a legacy user authentication database
  • ...

You can also modify the behavior of an out-of-the-box Account Provider through Custom Account Providers, but it might be better to contact us to incorporate the specific use case in the core.

For more information see Custom Account Providers

Custom Claim Providers

Custom Claim Providers allow you to retrieve and add user information from external resources, services, databases... after the user authenticated using the Account Provider,
but before the user is set as authenticated in The Identity Hub. The information can then be used by the applications.

For more information see Custom Claim Providers

Custom SMS Providers

Although The Identity Hub supports one out-of-the-box SMS Provider, you might need create a custom one when you want to use your existing mobile provider contract.

For more information see Custom Sms Providers

Custom Configuration

Custom configuration related to specifying your Azure Application Insights key, Google Analytics or Google Tag Manager settings can be done in the web.config by specifying the correct values in the AppSettings section.

For more information on the application settings you can configure see The Identity Hub configuration

SameSite cookies

As of February 2020 a new RFC will take effect as browsers start to roll-out their implementation of the new default behavior by treating cookies which do not specify SameSite by default as Lax.
Chrome and browsers based on chromium are announced to roll out first.

In respect to this The Identity Hub, which requires some cookies to be send cross site, might experience problems. To mitigate this problem, and during the migration phase, we advise you to opt-out of the new behavior by specifying an outbound rule in the web.config of your installation of The Identity Hub.

For more information see SameSite Outbound Rule in web.config