Automate Schedule lets you authenticate to the Automate Schedule server through your AD/LDAP server. This allows you to use existing user IDs for access to the Automate Schedule.

Note: Skybot Scheduler has been renamed to Automate Schedule and is now part of the Automate suite of products. The existing Skybot Scheduler features and functionality are the same; only the product name has changed.

 

Transcript

Authenticating with Active Directory/LDAP

Skybot Scheduler includes support for authenticating to the Skybot server through your active directory server. This features reduces initial set up time and also ongoing user maintenance by allowing you to use your existing user IDs for access to the Skybot Scheduler.

Options for Authentication Type

The authentication option is under system settings. If you select "edit" under authentication configuration, you will see that you have three options here for authentication type. The "Use Skybot" authentication option is the default upon completion of your installation. This option requires you to create users within the Skybot server. You have two options for using LDAP for authenticating to the Skybot server. If you use the "LDAP Authentication," you still must create the Skybot scheduler users within the Skybot product. But when those users log in, their password will be validated using the LDAP server. If you select "Use LDAP Authentication with User Authorization," then Skybot Scheduler will import those users directly from your AD or LDAP server. No user set up is required within the Skybot Scheduler product.

Configuring the Authentication

Set up for both of these options is the same. To configure the authentication, you simply enter the name of your host and also port for communication with the AD server. Also check if SSL is required for communication with the server.

Next, you enter the LDAP administrator information from your server. Our example shows the distinguished name format for our administrator. You also must enter the password for the administrator and the password is encrypted so it will not display.

User Roles in Skybot Scheduler

Next, you enter the context for your users in the distinguished name format so that Skybot can find the users. And the nfinally the fields for the attributes that will be used by Skybot to validate those users. If we take a look on our LDAP server, we can see here in the active directory administrative center that I have created three groups: my administrator group for Skybot, an operations group, as well as a user group. And the properties in this group will show me where I would add the members and these are the members that I have got in my Skybot server. And also,l if I need to find a formatting for that distinguished name, I can find that information here as well.

So then once you have that set up, if you go to the roles that are created for Skybot Scheduler...if I take a look at this user role, this is the mapping to my group that is set up on my AD server and here I can determine the type of authority that each user will receive. Here you can see that, as users log in to the Skybot Scheduler, the type of authority that each user will receive. Here you can see that, as users log in to the Skybot Scheduler using their network ID and password, they will be authenticated by the AD server and automatically imported into Skybot Scheduler. So that's it. It's pretty simple. So please contact us at skybotsoftware.com if you have any additional questions.


Still have questions? We can help. Submit a case to Technical Support.

Last Modified On: March 11, 2019