Many of our on-premise customers have integrated Spira with their Microsoft Active Directory (AD) infrastructure using our LDAP integration option. When they want to move to the cloud, they need to switch their users from LDAP to Single Sign On (SSO) using an Oauth based option such as ActiveDirectory Federated Services (ADFS) or AzureAD. This article describes the process.
Spira and KronoDesk let you import existing users from LDAP into the system. That will bring over the users, and also link their user profile to their LDAP user by means of the LDAP Distinguished Name (or DN). However if you move a user in the LDAP folder structure, it may break the link with Spira, resulting in that user not being able to login.
Integrating SpiraTest, SpiraPlan or SpiraTeam with your LDAP or ActiveDirectory direcory server makes a lot of sense. It allows you to have a single user authentication system, with all logins and passwords centrally managed. Spira includes integration out of the box with LDAP and this article provides help for some common issues that we have come across.
Sometimes users have more complex LDAP configurations. For example, users may have two different "Base DN"s where the users are located. They want to know - if there a way somehow to define two different "Base DN"s ?