advertisement
Authentication
Overview
All users are defined in Tracking using the Administration module.
Behind the CLIENT firewall: on premise
l l l
Product Authentication: This is the standard out of the box means of logging into Tracking. User IDs and passwords validated by the SendSuite Tracking application.
Auto-logon supported by Windows authentication: Password verification is disabled when users are successfully logged into the corporate PC, The Tracking User ID must be the same as the user’s
Windows ID. Auto-logon uses .NET to obtain the Windows credential from the client workstation.
Auto Logon is only available for deployments behind your company’s firewall.
LDAP using Active Directory: Interactive login not validated by the SendSuite Tracking database.
Users are validated by the LDAP host.
NOTE: A valid user account must first be created or already exist within SendSuite Tracking in order for any user to access the system. Passwords are validated by the system in Product authentication mode. In LDAP mode the user ID and password are validated against the configured LDAP host system. In Auto-Logon or Key
Exchange authentication modes the system only validates the user ID but not the password. Key Exchange makes use of a unique access token that, when configured, is automatically provided by the client workstation.
Hosted deployment
l l
Product Authentication: This is the standard out of the box means of logging into Tracking. User IDs and passwords validated by the SendSuite Tracking application.
Key Exchange: Intended for SendSuite Tracking installations in hosted environments, Key Exchange
Auto-Logon emulates the SSO user experience. SendSuite Tracking generates a client key for each software instance during the installation of the application server software. A new key can be generated if necessary by a server administrator. Each enterprise is provided with their key to use during the SendSuite Tracking client installation process. Once installed and configured, SendSuite
Tracking generates an access code based on the user ID, a unique token, and client key, and grants access if it matches the code generated by the application server.
Note that login requires access to the client key and access code creation method, and that each login requires unique authentication. A new key can be generated if necessary.
SendSuite
®
Tracking Technical Specification 19
advertisement
Related manuals
advertisement
Table of contents
- 1 Introduction
- 1 Overview
- 2 System Configuration
- 2 Overview
- 2 Server communication
- 3 Environment Descriptions and Considerations
- 4 Stand-alone Single User Workstation
- 5 Single Server
- 7 Multi Server
- 8 Web Farm, Clustered Database and Load Balancer
- 9 Dispersed WAN
- 10 Multi Location/Multi User WAN System Configuration
- 11 Hosted Deployment
- 12 TAPlus Data Collectors
- 12 Data Collection Communications Diagram
- 13 TAPlus Data Record Maximum Specifications
- 14 Synchronization Diagram
- 15 Minimum Hardware Operating System Requirements
- 15 Application Server
- 17 Database Server
- 18 Virtual Machine Environments
- 18 Microsoft SQL Server Licensing Considerations
- 19 Authentication
- 19 Overview
- 19 Behind the CLIENT firewall: on premise
- 19 Hosted deployment
- 20 SendSuite Tracking Software Installation
- 20 Software Deployment Diagram
- 20 Pre-Installation Security/Permissions
- 21 Components of SendSuite Tracking
- 21 Client
- 21 Designer
- 21 Administrator
- 21 Tracking SQL Database Environment
- 22 Support Files
- 22 VFP Runtime Library
- 22 Table Identification
- 22 System Tables (SQL)
- 25 Support Tables (SQL)NOTE: The list below is applicable with SendSuite Tracki...
- 26 Supported Barcode Peripherals
- 26 Supported Tracking Assistant Plus Devices
- 28 Barcode Scanners