As of the writing of this blog, Incident Tracker currently handles Account Management in the following ways.
CLOUD / HOSTED Incident Tracker
Right now in the Cloud, there is only one method for managing accounts. That method is to use the built-in tools to create and manage users. This method is stand-alone and has no direct relationship with any other user database such as Microsoft Active Directory (however user accounts can be exported out of any user database and imported into Incident Tracker, but there is no synchronization between accounts after this process). However, the development team is actively exploring using Microsoft Active Directory Federation Service to allow the Incident Tracker Cloud solution to potentially communicate with a customers Active Directory database. Look for more on this in the coming months.
On-Premise Incident Tracker (customer hosted)
For Customers who lease or purchase Incident Tracker to be run privately on their own hardware and network, there are three account management methods.
The first is the native Incident Tracker account tools that are available in the cloud. Accounts are managed through the tools available in Incident Tracker and have no relationship (other than doing a one-time import) from any other account databases.
The second method is to create an account or group of accounts that synchronize with Microsoft Active Directory. This method requires only that the customer be able to communicate with their LDAP services. In this scenario, users log in to Incident Tracker using their Active Directory credentials.
The last method is Single Sign-on via windows and Internet Explorer. In this scenario, Incident Tracker uses the Windows account already logged in to the device to automatically authenticate into the application. This method requires a customized scope of work and requires the Incident Tracker team to work with customer IT engineers and is only supported with the Internet Explorer browser.
As mentioned above, the Incident Tracker development team is currently working on federating accounts between the Cloud and customers’ private Microsoft Active Directory database. As this process comes closer to being certified we will post more information and alert our customer base to how this will work.