Integrated Authentication
Institutions can validate J1 Desktop application users using integrated authentication.
With this method, the J1 Desktop application uses the J1 Desktop application user's
Windows credentials to grant them access to windows and processes within
J1. When using integrated authentication, users are not required to log
in. For tighter security, the is recommended. This authentication method also
utilizes Active Directory; however, the user is required to log in.
To use integration authentication
and synchronize J1 users and groups:
- Create an Organizational Unit (OU) in your
Active Directory to be used solely for specifying J1 Desktop application users,
application groups, and membership of those users in application groups.
Outside the initial implementation steps, J1 Desktop application users,
J1 Desktop application groups, and group memberships can be added in Active
Directory and a Jenzabar-provided SQL Server Agent job synchronizes
them to the APP_USER, APP_GROUP, and GROUP_MEMBERSHIP tables in the
J1 database with the information in Active Directory.
· Use J1
Security and Permissions (Tasklist) to manage function permissions for
each group. These group function permissions are not contained or maintained
in Active Directory; therefore, the J1 Security and Permissions (Tasklist)
module must be used to maintain that information.
To
use integration authentication and synchronize
just J1 users (available for 6.5.6 and 7.2.0 or higher schools only):
- Create an OU in your Active Directory to be
used solely for specifying J1 Desktop application users. Outside the
initial implementation steps, J1 Desktop application users can be added in
Active Directory and the Jenzabar-provided SQL Server Agent job synchronizes
them to the APP_USER table in the J1 database with the information
in Active Directory.
- Use the J1 Security and
Permissions (Tasklist) module to manage the J1 group security memberships
and permissions for each group. These permissions are not contained
or maintained in Active Directory; therefore, the J1 Security and
Permissions (Tasklist) module must be used.
To Learn More...
Implementing
Active Directory for J1
Accessing Additional Reports
Third-Party Access using Integrated Authentication
Integrated
Authentication with Login Prompt