Hi,
We have a scenario where a lot of contacts is connected to multiple accounts. (N:1 between account and contact).
We do not want to have this scenario when starting with portals. We want to keep the functionality related to filtering lists, security and creating new records close to the standard functionality where a contact is only connected to one account. (the contact should choose which account he/she should work with during sign in.)
We will use external identity provider and we consider a solution where the user sign in to the portal/external identity and decide which account to work with based on a list of available accounts for the contact (this process will be outside the portal before the user is forwarded to the portal) If a contact is connected to 3 accounts we will create 3 alternative contacts, each mapped to only one account. Based on the account that the user selects during sign in we will forward the correct alternative contact (that is mapped to only that account) to the portal. We will use a custom claim in the token to tell the portal which contact this is. So the short question is:
Insted of authenticate the contact based on username and email can we authenticate a user based on custom claim and email?
