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 8 changed one line
[{$applicationname}] users enter the [{$applicationname}] Professional system through the login screen:
[{$applicationname}] users enter the [{$applicationname}] Professional system through the login screen:
At line 11 changed one line
;[User Password|USER_PASSWORD]:A user password must be provided to authenticate the person logging in. The password field is masked with asterisks as it is entered to keep it confidential. Passwords may be up to 16 alphanumeric characters; they are encrypted in the database. Passwords are initially generated by the system but may be subsequently maintained by the eP user or a security administrator.
;[User Password|USER_PASSWORD]:A user password must be provided to authenticate the person logging in. The password field is masked with asterisks as it is entered to keep it confidential. Passwords may be up to 16 alphanumeric characters; they are encrypted in the database. Passwords are initially generated by the system but may be subsequently maintained by the [{$applicationname}] user or a security administrator.
At line 134 changed one line
%%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.%%
%%information The term “PIN” and “Password” can be used interchangeably. Self Service passwords are normally referred to as PIN numbers to differentiate them from [{$applicationname}] User and Candidate passwords.%%
At line 149 changed one line
!Resetting eP User Passwords
!Resetting [{$applicationname}] User Passwords
At line 161 changed one line
Self Service PIN numbers can be reset by security administrators through either the IMRE-Reset Self Service PIN screen or through the Self Service Access tab on the IEID-Maintain Identity Information screen within the eP Professional application. Access can be restricted to specific personnel records in both of these functions by setting up appropriate security rights.
Self Service PIN numbers can be reset by security administrators through either [IMRE] or through the Self Service Access tab on [IEID] within the [{$applicationname}] Professional application. Access can be restricted to specific personnel records in both of these functions by setting up appropriate security rights.
At line 183 changed one line
Many different types of users use the ePersonality system – eP Professional users (eP users), Self Service users and Candidates. All of these different types of users are referred to as “accessors” of the system. ePersonality uses a consistent approach for managing all accessors of the system.
Many different types of users use the [{$applicationname}] system – [{$applicationname}] Professional users, Self Service users and Candidates. All of these different types of users are referred to as “accessors” of the system. [{$applicationname}] uses a consistent approach for managing all accessors of the system.
At line 194 changed 2 lines
Each type of ePersonality user has a specific way of being authorized to access the system.
*eP users are created and authorized through the IMUS screen.
Each type of [{$applicationname}] user has a specific way of being authorized to access the system.
*eP users are created and authorized through [IMUS].
At line 200 changed one line
Below is a description of each of the different ways users can be authorized in ePersonality.
Below is a description of each of the different ways users can be authorized in [{$applicationname}].
At line 202 changed 3 lines
!Authorizing eP Users
eP users are maintained by security administrators through the [IMUS] within the eP Professional application. Users created through [IMUS] are stored in the [P2K_AM_USERS] table and also become Oracle users. This function should be highly secured.
!Authorizing [{$applicationname}] Users
[{$applicationname}] users are maintained by security administrators through the [IMUS] within the eP Professional application. Users created through [IMUS] are stored in the [P2K_AM_USERS] table and also become Oracle users. This function should be highly secured.
At line 213 changed one line
;[Access Tab|]:This section contains the access information that is used by ePersonality. Refer to the Common Accessor Information section for a detailed description.
;[Access Tab|]:This section contains the access information that is used by ePersonality. Refer to the [Common Accessor Information|USER PASSWORDS#CommonAccessorInformation] section for a detailed description.
At line 237 changed 4 lines
Refer to the [Common Accessor Information|USER PASSWORDS#CommonAccessorInformation]
section below for a detailed description.
Refer to the [Common Accessor Information|USER PASSWORDS#CommonAccessorInformation] section below for a detailed description.
At line 240 added one line
At line 316 added one line
At line 318 added one line
At line 320 added one line
At line 322 added one line
At line 324 added one line
At line 362 added one line
At line 364 added one line
At line 364 changed one line
In P2K, password control is set at the client site level through the IMST-Maintain Client Site Information screen. This information is still maintained in ePersonality but it is only used for the P2K users.
In P2K, password control is set at the client site level through [IMST-Maintain Client Site Information[. This information is still maintained in ePersonality but it is only used for the P2K users.
At line 367 changed one line
ePersonality uses new password generation techniques based on industry standards. Sophisticated security options are provided for clients who wish to tighten their security. However, for compatibility reasons, P2K password information may be kept in tact until clients no longer need to use P2K. If this is done, users will still be able to login to P2K and run certain P2K processes
ePersonality uses new password generation techniques based on industry standards. Sophisticated security options are provided for clients who wish to tighten their security. However, for compatibility reasons, P2K password information may be kept in tact until clients no longer need to use P2K. If this is done, users will still be able to login to P2K and run certain P2K processes.
At line 376 added one line
At line 378 added one line
This page (revision-39) was last changed on 26-Nov-2021 10:22 by jaikenTop