There are several built in single sign-on integrations included with
Morpheus . These can be configured via the IdentitySources button
in Admin->Accounts. These integrations include linking
capabilities with LDAP, Active Directory, Okta, and Jump Cloud. One can
even map these sign on tools to equivalent roles in Morpheus so at
first log in users are assigned the appropriate role.

Active Directory is Microsoft’s primary authentication service widely used in Enterprise organizations and even via Microsoft’s cloud services. While Active Directory also supports LDAP protocol support (which Morpheus can integrate with as well), the main Active Directory integration can also be utilized. It is even possible to map Active Directory groups to equivalent Roles within Morpheus .

Note

To use Active Directory, a valid / trusted SSL certificate must be in place on the Active Directory services (self signed will not work).

Enter a role if OneLogin users logging into morpheus must have at least this OneLogin role to gain access to Morpheus.

DEFAULT ROLE

The default Morpheus Role applied to users created from OneLogin Integration if no other role mapping is specified below

ROLE MAPPINGS

Existing Morpheus Roles will be listed with fileds to enter OneLogin Roles to map to. Users with OneLogin roles matching the role mappings will be assigned the approprie Role(s) in Morpheus when sigining in.

Select SAVE CHANGES and the OneLogin Integraitnn will be added.

Users can now login to Morpheus with OneLogin credentials. The first Login will create a user in Morpheus matching the Username, email and Password from OneLogin. If a REQUIRED ROLE is specified in the Identiry Source settings, only users with that Role in OneLogin will be able to login to Morpheus.

Important

OneLogin users will not authenticate in Morpheus if there is an existing Morpheus User with matching username or email address.