|
Results |
|
Last Login date not updated for new user, user was logged to SWC
Create new user account (user1) in App Administrator with regular product access Login to Work Center by newly created user user1 Look at the user details in the App Administrator.
|
|
|
STIG V-69355 - Application must display the time and date of the users last successful logon
STIG V-69355 - Application must display the time and date of the users last successful logon
|
|
|
"Users" system report may report incorrect time values for "Last Login Date"
"Users" system report may report incorrect time values for " Last Login Date "
|
|
|
After login and click on Calendar, get error "You did not have a privilege required to complete your last action"
1) In the Release Train application, create one or more Dashboard report of type Calendar Feed. For example, you may have one report that looks at Prod Start and Prod End dates and a separate report that looks at Deploy Start and Deploy End dates . When you save these reports, be sure to save them as Guest reports.
|
|
|
Periods in Login IDs can cause problems if Request Filtering is enabled in IIS
When a Login ID in SBM contains periods and you try to perform an action that will pass the Login ID as part of the header's request URL, the ISAPI filter on the IIS server will grab it believing that you are requesting a file with a specific extension with the extension being whatever follows the last period in your Login ID. This only seems to pose a problem if the customer has Request Filtering enabled in IIS where you have to create an "allowed" list of file extensions that can be requested.
|
|
|
Current User Activity System Report shows users last accessed for up to 1 hour even if session timeout is 5 minutes
- Set the Session Timeout to 5 minutes - log in a few users to this SBM system - wait 30 minutes
|
|
|
User report exported to Excel shows date of 12/31/1969
When they run the System Report > Users, if there is no ' Last Login Date ', then when it is exported to Excel, that field is populated with the date of 12/31/1969. To reproduce the problem: Open SBM UI > Reports > Browse System Reports > Users.
|
|
|
DIM10: Report error in desktop client using a Date attribute
DBI0004527E: DBIO: Database I/O error occurred SQL-1830(02ADD2B8) ORA-1830: date format picture ends before converting entire output string" If you logout and login again to Desktop Client the final Oracle error is not generated if you attempt to rerun the report.
|
|
|
Dim10: Web Client and Admin Console return or recycle back to the login screen when trying to login.
The first character must be an alpha character. The last character must not be a minus sign or period . ..... Single character names or nicknames are not allowed.
|
|
|
When Auto-logout logs an SBM user off, the license-timeout is reset to 60 minutes from the point of logout.
When SBM has Auto-logout enabled, and the configuration is not using SSO as the login handler, the 60 minute license-timeout clock is reset to the time the user is logged off as opposed to leaving it at the time of their last activity.
|
|
|