10.1 Release Notes

Introduction

TrustBuilder.io suite consist of 3 products:

  • TrustBuilder.io, the cloud instance of the TrustBuilder.io suite that allows easy connections towards standardized applications and identity providers.
  • TrustBuilder IDHub, the customer specific instance of the TrustBuilder.io suite which allows customizable connections for the customers’ unique environment. This instance can run on the customer premise (local, private cloud or public cloud) as well as in a SaaS environment managed on TrustBuilder.io.
  • TrustBuilder Mobile Authenticator, the strong authentication solution for mobile devices combining the world’s safest authentication method with the best user login experience.

Trustbuilder.io

Quick Config Framework for applications and identity providers.

The quick configuration framework allows customers to deploy new identity providers and applications in a fast, reliable and secure manner. In a few simple steps, new identity providers are activated and connected to your applications. New applications are activated with an easy to use wizard.

  • The first available identity providers are[KB1]:
    • Itsme
    • Idin
    • Facebook
  • The first available applications will come soon
  • To view the full list of applications and identity providers please look at: 
    • https://www.trustbuilder.com/trustbuilder-io-suite/applications-and-services/
    • https://www.trustbuilder.com/trustbuilder-io-suite/identity-providers/
  • The available identity provider and applications are published on a separate SaaS server, independent of TrustBuilder releases. This allows faster deployment of new IDP’s and applications, faster updates in case of changes and allows us to deliver faster on our customer demands for specific applications and Identity providers. If your organization needs an application or identity provider that is not yet listed, please fill in your request via a zendesk ticket.

Trustbuilder Authenticator

  • TrustBuilder Mobile Authenticator is available as a stand-alone branded application or as an SDK that can be integrated in an existing mobile application. The TrustBuilder Mobile Authenticator can be used to strongly authenticate mobile applications as well as web pages through an out of band mechanism. TrustBuilder Mobile Authenticator requires TrustBuilder.io for easy provisioning and authenticating.
  • Added a new Mobile IDP Type on TrustBuilder.io and TrustBuilder IDHub to activate and configure TrustBuilder Mobile Authenticator.
  • Supports QR scanning for Mobile onboarding and authentication in cases where push authentication is not desired or possible. (eg, on shared browsers)
  • Supports push message authentication on iOS and android for passwordless authentication.
  • Support of device independent PIN and device biometrics for easy PIN replacement.
  • Supports multi-device registration and device binding. This allows integration of 1 license on multiple devices as welll as multiple applications on the same device. Each instance of the client will have a unique key, making management of multiple devices and applications more user friendly as well as more secure. The used mechanism allows unlimited devices and applications to be bound to 1 user.
  • Extended support for API based admin user management.
  • The old version of TrustBuilder for Mobile, which supported OATH is discontinued. TrustBuilder still supports OATH for third party authenticators, but the new mechanism for authentication is proven to be far more secure, reliable as well as user friendly. Should you still use a previous version of TrustBuilder authenticator, please contact info@trustbuilder.com for alternative options.

IDHub 10.1

Changes

  • Added support for Oauth 2.1(https://tools.ietf.org/html/draft-ietf-oauth-v2-1-01)
  • Added the option to make OIDC signed request objects required when configuring a Service Provider for easier transaction signing.
  • The ACR value of the authentication method is now sent along to the IDP for OIDC IDPs (for SAML IDPs this was already possible before) which allows a selection of the desired IDP when multiple options are available.
  • Improved the support for passing languages between templates
  • Changed API keystore entries to use second precision for dates
  • Several lay-out changes (to overview pages)
Bug fixes
  • Change password email wasn’t sent (TB-6812)
  • Resolved an issue that could reveal if a username was known in the system (TB-7019)
Was this article helpful?
1 out of 1 found this helpful

Comments

0 comments

Please sign in to leave a comment.