This page (revision-39) was last changed on 26-Nov-2021 10:22 by jaiken

This page was created on 26-Nov-2021 10:22 by jmyers

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
39 26-Nov-2021 10:22 30 KB jaiken to previous
38 26-Nov-2021 10:22 31 KB rforbes to previous | to last
37 26-Nov-2021 10:22 31 KB rforbes to previous | to last
36 26-Nov-2021 10:22 31 KB rmorrell to previous | to last
35 26-Nov-2021 10:22 31 KB rmorrell to previous | to last
34 26-Nov-2021 10:22 31 KB jmyers to previous | to last
33 26-Nov-2021 10:22 31 KB jmyers to previous | to last EMAIL_ADDRESS ==> EMAIL_ADDRESS(Disambiguation)
32 26-Nov-2021 10:22 31 KB jmyers to previous | to last
31 26-Nov-2021 10:22 31 KB jmyers to previous | to last
30 26-Nov-2021 10:22 31 KB jmyers to previous | to last
29 26-Nov-2021 10:22 31 KB jmyers to previous | to last
28 26-Nov-2021 10:22 32 KB jmyers to previous | to last
27 26-Nov-2021 10:22 32 KB jmyers to previous | to last
26 26-Nov-2021 10:22 33 KB jmyers to previous | to last
25 26-Nov-2021 10:22 33 KB jmyers to previous | to last
24 26-Nov-2021 10:22 33 KB jmyers to previous | to last
23 26-Nov-2021 10:22 33 KB jmyers to previous | to last
22 26-Nov-2021 10:22 33 KB jmyers to previous | to last
21 26-Nov-2021 10:22 33 KB jmyers to previous | to last

Page References

Incoming links Outgoing links
USER PASSWORDS
USER PASSWORDS

Version management

Difference between version and

At line 87 changed one line
Every successful login to ePersonality initiates a new application session. Session connection information and user context data is recorded on the P2K_AM_SESSION_AUDITS table in the database. The system tracks who has accessed the system, when they logged in and out, how they accessed it and what roles they had at the time of the session.
Every successful login to [{$applicationname}] initiates a new application session. Session connection information and user context data is recorded on the [P2K_AM_SESSION_AUDITS] table in the database. The system tracks who has accessed the system, when they logged in and out, how they accessed it and what roles they had at the time of the session.
At line 92 changed 7 lines
• Passwords must start with an alphabetic character
• Passwords cannot equal the user name
• Passwords cannot be a common phrase like welcome, database, account user, password, oracle, computer, etc. This is controlled through a lexicon X_BLOCKED_PHRASES.
• If a Minimum Password Size has been provided in the access rules, the password must be at least as long as the minimum length.
• If the Must Contain Digit option is chosen in the access rules, the password must contain a numeric digit.
• If the Must Contain Punctuation is chosen in the access rules, the password must contain at least one of the following characters: ! # $ % & ( ) ` * + , - / : ; < = > ? _
• Passwords cannot contain the following characters: " ' @
*Passwords must start with an alphabetic character
*Passwords cannot equal the user name
*Passwords cannot be a common phrase like welcome, database, account user, password, oracle, computer, etc. This is controlled through a lexicon [X_BLOCKED_PHRASES].
*If a Minimum Password Size has been provided in the access rules, the password must be at least as long as the minimum length.
*If the Must Contain Digit option is chosen in the access rules, the password must contain a numeric digit.
*If the Must Contain Punctuation is chosen in the access rules, the password must contain at least one of the following characters: ! # $ % & ( ) ` * + , - / : ; < = > ? _
*Passwords cannot contain the following characters: " ' @
At line 102 changed 8 lines
1st digit - random uppercase letter
2nd digit - random lowercase letter
3rd digit - random digit
4th digit - random digit
5th digit - random lowercase letter
6th digit - random lowercase letter
7th digit - random digit
8th digit - random digit
|1st digit|random uppercase letter
|2nd digit|random lowercase letter
|3rd digit|random digit
|4th digit|random digit
|5th digit|random lowercase letter
|6th digit|random lowercase letter
|7th digit|random digit
|8th digit|random digit
At line 115 changed 2 lines
!eP User Password Changes
eP users may change their own password through the IMCU-Change Password screen within the eP Professional application.
![{$applicationname}] User Password Changes
[{$applicationname}] users may change their own password through [IMCU] within the [{$applicationname}] Professional application.
At line 118 changed 8 lines
User Name
The user name defaults to the user who is currently logged in.
Existing Password
The existing password must be entered to authenticate the request.
New Password
A new password must be supplied
Confirm Password
The new password must be entered a second time to ensure that it has not been keyed incorrectly.
;[User Name|USER_NAME]:The user name defaults to the user who is currently logged in.
;[Existing Password|]:The existing password must be entered to authenticate the request.
;[New Password|]:A new password must be supplied
;[Confirm Password|]:The new password must be entered a second time to ensure that it has not been keyed incorrectly.
At line 129 changed 11 lines
Self Service users may change their own password through the WEDPN-Change My Pin screen within the Self Service application.
User Name
The user name defaults to the user who is currently logged in.
Existing PIN
The existing password must be entered to authenticate the request.
New PIN
A new password must be supplied
Confirm PIN
The new password must be entered a second time to ensure that it has not been keyed incorrectly.
The term “PIN” and “Password” can be used interchangeably. Self Service passwords are normally referred to as PIN numbers to differentiate them from eP User and Candidate passwords.
Self Service users may change their own password through the [WEDPN] screen within the Self Service application.
;[User Name|]:The user name defaults to the user who is currently logged in.
;[Existing PIN|]:The existing password must be entered to authenticate the request.
;[New PIN|]:A new password must be supplied.
;[Confirm PIN|]:The new password must be entered a second time to ensure that it has not been keyed incorrectly.
%%information The term “PIN” and “Password” can be used interchangeably. Self Service passwords are normally referred to as PIN numbers to differentiate them from eP User and Candidate passwords.%%
At line 144 changed 9 lines
User Name
The user name defaults to the user who is currently logged in.
Existing Password
The existing password must be entered to authenticate the request.
New Password
A new password must be supplied
Confirm Password
The new password must be entered a second time to ensure that it has not been keyed incorrectly.
;[User Name|]:The user name defaults to the user who is currently logged in.
;[Existing PIN|]:The existing password must be entered to authenticate the request.
;[New PIN|]:A new password must be supplied.
;[Confirm PIN|]:The new password must be entered a second time to ensure that it has not been keyed incorrectly.
At line 154 removed 14 lines
!P2K User Password Changes
P2K users may change their own password through the IMCU-Change Password screen within P2K.
User Name
The user name defaults to the user who is currently logged in.
Old Password
The old password must be entered to authenticate the request.
New Password
A new password must be supplied
Confirm Password
The new password must be entered a second time to ensure that it has not been keyed incorrectly.
Password validation is done as soon as the user clicks OK. If the validation fails, the user is notified in a dialog. Password changes that pass the validation are effective immediately.
When a user changes their password, as soon as the password is accepted, the user will be automatically logged out of the system and will be required to log in again with their new password.
At line 172 changed one line
eP user passwords can be reset by security administrators through either the IMRU-Reset ePersonality User Password screen or through Access tab on the IMUS-Maintain User Profiles screen within the eP Professional application. These functions should be highly secured.
[{$applicationname}] user passwords can be reset by security administrators through either the [IMRU] screen or through the [IMUS Access|IMUS#Access] tab within the [{$applicationname}] Professional application. These functions should be highly secured.
At line 174 changed 10 lines
Find Block
The eP user whose password is to be changed must be located in the Find block on the top line.
New Password
A new password must be supplied or the “generate” toggle must be turned on.
Confirm Password
If the new password is being supplied, it must be entered a second time to ensure that it has been keyed correctly.
Or Generate New Password
This toggle must be turned on if the security administrator wants the new password to be generated by the system.
Force Password Change On Next Login
This toggle allows the security administrator to force the user to change their password on their next login.
;[Find Block|]:The eP user whose password is to be changed must be located in the Find block on the top line.
;[New Password|]:A new password must be supplied or the “generate” toggle must be turned on.
;[Confirm Password|]:If the new password is being supplied, it must be entered a second time to ensure that it has been keyed correctly.
;[Or Generate New Password|]:This toggle must be turned on if the security administrator wants the new password to be generated by the system.
;[Force Password Change On Next Login|]:This toggle allows the security administrator to force the user to change their password on their next login.
This page (revision-39) was last changed on 26-Nov-2021 10:22 by jaikenTop