Incident Tracker is offered in two ways. The most popular deployment method is could-based, where the customer is given a URL and can securely access Incident Tracker over the internet. The other option is on-premise. In the on-premise option the customer has access to the exact same software but it runs on their own private environment. With on-premise the customer supplies the hardware and environment needed to run Incident Tracker. There are pros and cons to each deployment method. Cloud is very simple to set up and get running and requires nothing on the customers end. On-premise requires the customer set and configure the environment (along with help from an Incident Tracker technician) and provide system maintenance, responsible for backups, etc… However in this case the customer has more control over access and security and can also utilize Microsoft Active Directory’s LDAP service to set up a true single sign on or a same sign on environment for users.
The LDAP synchronization service can be used in conjunction with native Incident Tracker authentication as well, so as the application administrator you can create backdoor Incident Tracker accounts to use for site maintenance that would not rely on your Active Directory network, while all other users accounts could. This flexibility gives you the power to create your own business practice in how you manage the software.
Below is a sample screen capture of what the LDAP tools look like (showing some of our internal test accounts)