Possible categorizations for whether accounts are reported as Service “Compliant w/3-year Account Mandate?” are: YES (account is compliant). *** NO <---- MUST FIX *** (date created and date verify code last changed > 3 years in the past). No, but user active. not UNABLE TO DETERMINE (until patch XU*8.0*574, date verify code last changed for Connector Proxy accounts was incorrectly recorded as 4/10/2005) Unable to determine but active. not If an Date Verify Code Last Changed is listed as but date not account’s “(changed recorded)”, that means the date is present, and unless the account was created within the “fake” 4/10/2005” last 3 years, it is impossible to determine if the account is in compliance with the 3-year mandate. Also, if there is a value in the XUS LOGON ATTEMPT COUNT field, that value is displayed, as it could indicate a remote system attempting to connect and failing with an invalid Verify code. If the option to connector proxy is selected, the following checks are “Check/display fields?” performed: Warnings: (any field listed in the warning section should be populated. However, not before changing, consult the National Help Desk or Customer Support as some applications may (currently) be depending (incorrectly) on a misconfigured connector configuration.) Values for other fields allowed/expected: (field normally populated for connector proxies). Other Fields Populated (not expected fields, but problematic either). not Other Multiples Populated (not expected, but problematic either). not If the option to sign-on log for connector proxy is selected, the report scans the “Scan activity?” sign-on log for all signon activity associated with the account. Any activity found is displayed, organized by client IP address, and within IP address, by date of signon. The purpose of this report section is to help sites determine which accounts are active, and which external systems (by IP address) are logging onto the site with the specified account. This helps determine which remote applications a change to the account (e.g., Verify code change) might impact, and also helps a site determine whether too many remote applications/data centers are using the same account (which could result in a more widespread service disruption if an account be must changed). NOTE: This option can be scheduled.
Possible categorizations for whether accounts are reported as “Compliant w/3-year Service Account Mandate?” are: YES (account is compliant). *** NO <---- MUST FIX *** (date created and date verify code last changed > 3 years in the past). No, but user not active. UNABLE TO DETERMINE (until patch XU*8.0*574, date verify code last changed for Connector Proxy accounts was incorrectly recorded as 4/10/2005) Unable to determine but not active. If an account’s Date Verify Code Last Changed is listed as “(changed but date not recorded)”, that means the “fake” 4/10/2005” date is present, and unless the account was created within the last 3 years, it is impossible to determine if the account is in compliance with the 3-year mandate. Also, if there is a value in the XUS LOGON ATTEMPT COUNT field, that value is displayed, as it could indicate a remote system attempting to connect and failing with an invalid Verify code. If the option to “Check/display connector proxy fields?” is selected, the following checks are performed: Warnings: (any field listed in the warning section should not be populated. However, before changing, consult the National Help Desk or Customer Support as some applications may (currently) be depending (incorrectly) on a misconfigured connector configuration.) Values for other fields allowed/expected: (field normally populated for connector proxies). Other Fields Populated (not expected fields, but not problematic either). Other Multiples Populated (not expected, but not problematic either). If the option to “Scan sign-on log for connector proxy activity?” is selected, the report scans the sign-on log for all signon activity associated with the account. Any activity found is displayed, organized by client IP address, and within IP address, by date of signon. The purpose of this report section is to help sites determine which accounts are active, and which external systems (by IP address) are logging onto the site with the specified account. This helps determine which remote applications a change to the account (e.g., Verify code change) might impact, and also helps a site determine whether too many remote applications/data centers are using the same account (which could result in a more widespread service disruption if an account must be changed). NOTE: This option can be scheduled.