The logged-in user’s name and assigned role appear at the end of the top navigation bar in the ODDC Server browser-based user interface.
|
Capability |
Regular (Data verification operator) |
Advanced (Project setup operator) |
Administrator |
|---|---|---|---|
|
View projects and batches |
Yes |
Yes |
Yes |
|
Use document/data verification |
Yes |
Yes |
Yes |
|
Create, update, or clone projects and batches |
No |
Yes |
Yes |
|
Delete batches or projects |
No |
No |
Yes |
|
View the Status page |
No |
Yes |
Yes |
|
Open the Logs page |
No |
Yes |
Yes |
|
Manage licenses |
No |
No |
Yes |
|
Manage users |
No |
No |
Yes |
Windows users #
Windows identities are stored normally as DOMAIN\username or MACHINE\username, with an empty password hash. A Windows identity that is not registered and not active cannot use the application.
Windows-authentication users cannot sign in through HTTP Basic because they have no application password. They must use Negotiate authentication.
Basic-authentication users #
For Basic users, the username is the value stored. Passwords are stored as hashes. The same account can use the browser login page when application authentication is set to Basic, and HTTP Basic on the Integrations API.
User-management safeguards #
The Users page lets an Administrator create users, assign roles, activate or deactivate accounts, edit names and roles, reset Basic-user passwords, and delete accounts. The application prevents an administrator from editing, resetting, or deleting it’s own admin account currently in use. Maintain at least two tested Administrator accounts so one administrator can recover the other.