Applies to Version 1.14 or higher

Introduction

When using 3rd Party Identity Providers (IDP) in IBSS, the platform carries out two actions. First, the platform will periodically synchronise the user details to IBSS so that the details can be verified when  a user logs in. Second, when a user logs in via their IDP, these credentials are matched to a record in the database.   

Historically, the matching process was against the email address field of the user account. For the vast majority of deployments this mechanism works, however there are some cases where it does not. In scenarios where a customer domain is made up of a number of child domains, the details that a user logs into the sub-domain with does not necessarily match the email address. In these cases, when using Azure Active Directory as the IDP caused the user to not be found when trying to login in the IBSS platform.

New Behaviour

Going forwards, the IBSS platform will now synchronise the usernames and email addresses of users across all sub domains. This will result in a slight change of behaviour logging into the IBSS client applications when using Azure Active Directory: 

!! Use your username when entering in your details when logging into Roamer or Flex !!

The current S14 release of the client apps will continue to ask for email address of the user. 
In this field please enter in your username instead. 
Going forwards the login dialogs will be updated.