Learn More: View Technical Details
Important
Information and features vary according to the roles to which you belong and the permissions associated with those roles. For more information, contact your module manager or your campus support team.
The View Technical Details window shows authentication information for the selected user.
Column | Description | Possible Values | Potential Resolution |
|---|---|---|---|
USER_ID | USER_ID value from the APP_USER table | ||
Authentication Type | Noted in the APP_USER and APP_USER_LDAP tables | AD Authenticated SQL Authenticated | |
Authentication Conflict | DB Principal for AD Name means a SQL Server database user account exists with the same name as the APP_USER.USER_ID | DB Principal for AD Name None | AD Authenticated users should generally not have SQL Server database user accounts for their USER_ID |
SQL Login User | Matches the APP_USER.USER_ID to the SQL Server Login and SQL Server database user accounts | SQL Login-User Found No SQL User No SQL Login | Create the missing login, database user, or rename the accounts to remove SQL aliased users |
SQL Server Login | Does the USER_ID from APP_USERS have a matching SQL Server Login? N\A for AD Authenticated accounts | Login Name Match LOGIN-APP_USER MISMATCH N\A | Create or correct the SQL Server login or APP_USER row so that a matching set is created |
SQL Server DB User | Does the USER_ID from APP_USERS have a matching SQL Server Database User? N\A for AD Authenticated accounts | DB User Name Match DB USER-APP_USER MISMATCH N\A | Create or correct the SQL Server database user or APP_USER row so that a matching set is created |
J1 Web User | Is the USER_ID a J1 Web User? | Y or N | Correct on the J1 Web System Users page or Desktop Users window |
Application User Active | The J1 Desktop active status; does not impact J1 Web | A or I | Correct on the Desktop Users window |
ID_NUM | The ID_NUM as set on the APP_USER row, matched up with a NAMEMASTER row | Must be present for J1Web users | |
NAMEMASTER_APPID | NAMEMASTER.APPID value | Must be present for J1Web users | |
NM NULL First Name | NAMEMASTER.FIRST_NAME | Y (First Name is NULL) N (First Name is NOT NULL) | |
NM NULL Last Name | NAMEMASTER.LAST_NAME | Y (Last Name is NULL) N (Last Name is NOT NULL) | |
PersonAppID | Person.AppID connected with the NAMEMASTER row | Must be present for J1Web users | |
PartyAppID | Party.AppID connected with the Person row | Must be present for J1Web users | |
PartyRoleAppID | PartyRole.AppID connected with this users Party row | Must be present for J1Web users | |
RoleType | RoleType associated with the PartyRole row | ApplicationUser (only valid value for users) | |
PartyRole Count = 1? | How many PartyRole rows are associated with the user' Party row? | 1 | Must only be 1. If more than 1, the invalid rows(s) must be determined and removed |
ApplicationUserAppID | The ApplicationUser.AppID connected with the PartyRole.AppID | Must match the PartyRole.AppID noted | Clear out the bad data and use the J1 Desktop Users window to mark the user as a J1Web User again |
UserAuthenticationAppID | The AppID from the UserAuthentication row associated with the ApplicationUser row | Must be present for J1 Web users | |
UserAuthenticationSID | The UserAuthentication. UniqueIdentifierCode value | Must be present for J1 Web users | |
AuthenticationSID | The SID used for authentication | APP_USER_LDAP.LDAP_OBJECT_SID (for AD authenticated accounts) sys.database_principals.sid for SQL Server authenticated accounts | |
SUSER SID | The SUSER_SID the SQL Server notes for the USER_ID | ||
SID Match | Do the noted SIDs match? | SID MISMATCH SID Match | The DSU has a post-update script named 052_Fix_Mismatched_SIDs.sql that corrects most mismatched SID issues |
PRINCIPAL ID | The PRINCIPAL_ID from the APP_USER row | Must be present for J1 Web users | |
ApplicationUser Principal ID Match? | Do the APP_USER.PRINCIPAL_ID and the ApplicationUser.PrincipalID match? | Principal ID MISMATCH Principal ID Match | The correct Principal ID must be determined, and the invalid one updated to the valid value |
SECURITY_OWNER Principal ID Match? | Do the APP_USER.PRINCIPAL_ID and the SECURITY_OWNER. PRINCIPAL_ID match? | Principal ID MISMATCH Principal ID Match | The correct Principal ID must be determined, and the invalid one updated to the valid value |
SECURITY_OWNER Exists? | Does the SECURITY_OWNER row exist? | Y or N | If N, create the missing SECURITY_OWNER row |