Regular readers and users know there’s very little you can’t do with Macro Scheduler. We see it being used for all kinds of applications and interfaces. The list is endless. Most solutions we see are unique to the customer’s specific scenario. But here’s something which almost every company could benefit from: Single Sign-on.
Single sign-on (SSO) is a property of access control of multiple related, but independent software systems. With this property a user logs in once and gains access to all systems without being prompted to log in again at each of them.
In many organisations users work with a multitude of disparate systems. A lot of time is wasted logging in and out of these systems.
At one of our clients we’re working on a Single Sign-on pilot driven by Macro Scheduler. This is an interesting and exciting use of Macro Scheduler which will benefit a large number of users across the organisation.
We also aim to have Macro Scheduler maintain the context between the different systems as logging in is only part of the problem. Usually users need to pull up records for the same customer, or order (for example) in each of those systems. If the single sign-on solution does that for them – and monitors when the context changes and mirrors that in the other systems, an awful lot of time can be saved, and chances for error are eliminated.
Macro Scheduler can handle LDAP lookup, access user information from databases, perform WEB/SOAP/COM interactions and, of course, can simulate user input for web and desktop applications which offer no alternative.
Macro Scheduler is an inexpensive and flexible solution which can work with any type of user interface, making it ideal for providing a single sign-on solution.
If you have done something similar with Macro Scheduler I’d be interested to hear from you. Comment below or drop us a line.
