TACACS+ Management Configuration Page

kron pam uses its own tacacs+ server to authenticate users the kron pam tacacs+ configuration can be done easily from the kron pam web gui to configure tacacs+ navigate to administration > tacacs management fill in all the required fields click save instance name the instance name the tacacs+ configurations will be applied to skip logging group user groups are not to be logged prompt username and password username/password prompt to display instead of the default prompt authorization exec service names this configuration option should be used if the device is not using the standard service exec paloalto and ppp options can be set cache update interval the cache update interval time can be changed and specified using this field during this cache interval, configuration changes in kron pam will not affect the tacacs server log settings the log level can be changed using the checkboxes debug, info, and error modes are available to check the logs ldap configuration settings if there is an ldap configuration in the kron pam setup wizard, it will be shown in the ldap configuration settings also, multiple ldap configurations can be added by using the add conf button the add conf button shows the following popup the fields and their meanings are as follows config name the name used to match with the externaldirectorysource attribute of the users these names should be matched with the ldap source name parameter in the ldap configuration settings on the ldap manager page for example, if there are more than two ldap settings in an environment, one ldap configuration is called as “ldap1” and the other one “ldap2” users from ldap1 and ldap2 will have externaldirectorysource attributes as ldap1 and ldap2 respectively in tacacs manager, config names should be set up in the same way so that the tacacs module reads the externaldirectorysource parameter for the users and authenticates them from the correct ldap source ldap servers ldap server url in the following format “ldap\ //10 10 10 10 389” or “ldaps\ //10 10 10 10 636” if there are multiple servers for the same ldap configuration, multiple url’s can be defined in the same field, separated by a space character as follows “ldaps\ //10 10 10 10 636 ldaps\ //10 10 10 20 636” in this scenario, the tacacs module would try to reach the first url, and if it gets a connection error, it tries to reach the second, etc ldap base ldap base dn (distinguished name) example “dc=example,dc=com” active directory this flag should be enabled if the integrated ldap server is an active directory server ad domain active directory domain name should be provided if active directory is enabled ldap auth type “rest” or “ldap” “ldap” is the default choice and should be selected if the tacacs module connects directly to ldap servers for authentication “rest” should be selected in cases that there is no direct connection between the tacacs module and the ldap servers (such as cases where tacacs module is installed on tenant network) in this case authentication is done via the kron pam authentication module rest auth url the url of the authentication module, in the format “http //10 20 30 40 8087”