...
- MCS account for user must exist
- Ideally, an HR interface takes care of automatic creation of MCS users
- In case the logged in user doesn’t exist in MCS, the user will not be able to use any MCS-dependant features like making reservations.
- Cobundu SSO (receiving following attributes from the identity provider: "MCS login ID", "First Name", "Last Name" and "E-Mail“)
- In case the “MCS login ID” attribute is not correctly mapped, the user will not be able to use any MCS-dependant features like making reservations.
A user logging in with Cobundu ID (tenant.ID) is recognized as being part of a tenant where SSO has been setup and Cobundu will automatically create a Cobundu account.
A user logging in with e-mail address is not yet supported (status 4/11/2020), but is foreseen to be implemented by latest Q1 of 2021. It uses a whitelist of e-mail providers (eg @spacewell.com or @mcs.be) to check the tenant.
More information on Cobundu SSO can be found in this presentation (keep in mind: Cobundu SSO only available for Go.cobundu.com and Personal Assistant)
| View file | ||||
|---|---|---|---|---|
|
...