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 5 changed one line
The [{$applicationname}] application tightly controls who can access the system. Strict security rules are enforced for all types of users - [{$applicationname}]users, Self Service users and Candidates.
The Personality application tightly controls who can access the system. Strict security rules are enforced for all types of users - Personalityusers, Self Service users and Candidates.
At line 7 changed 2 lines
![{$applicationname}] User Login
[{$applicationname}] users enter the [{$applicationname}] Professional system through the login screen:
!Personality User Login
Personality users enter the Personality 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 [{$applicationname}] 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 Personality user or a security administrator.
At line 13 changed one line
[{$applicationname}] users will only be allowed to use the system if their credentials match those on file and if there are no restrictions currently imposed on their access. They may be asked to change their password as soon as their login has been validated under any of the following circumstances:
Personality users will only be allowed to use the system if their credentials match those on file and if there are no restrictions currently imposed on their access. They may be asked to change their password as soon as their login has been validated under any of the following circumstances:
At line 18 changed one line
[{$applicationname}] users credentials are validated against the information coded on the [IMUS Access|IMUS#Access] tab and are subject to the security rules established in the [IMAR] screen. The database that the user will be connected to is identified in the URL that was used to start the application.
Personality users credentials are validated against the information coded on the [IMUS Access|IMUS#Access] tab and are subject to the security rules established in the [IMAR] screen. The database that the user will be connected to is identified in the URL that was used to start the application.
At line 20 changed 2 lines
![{$applicationname}] User Forgotten Passwords
If an [{$applicationname}] user forgets their password, they should click the Forgot Password button on the login screen.
!Personality User Forgotten Passwords
If an Personality user forgets their password, they should click the Forgot Password button on the login screen.
At line 33 changed one line
Self Service users enter the [{$applicationname}] Self Service system through the login screen:
Self Service users enter the Personality Self Service system through the login screen:
At line 38 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 [{$applicationname}] 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 Personality User and Candidate passwords.%%
At line 56 changed one line
Candidates enter the [{$applicationname}] Candidate Self Service system through the following login screen:
Candidates enter the Personality Candidate Self Service system through the following login screen:
At line 87 changed one line
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.
Every successful login to Personality 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 117 changed 2 lines
![{$applicationname}] User Password Changes
[{$applicationname}] users may change their own password through [IMCU] within the [{$applicationname}] Professional application.
!Personality User Password Changes
Personality users may change their own password through [IMCU] within the Personality Professional application.
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 [{$applicationname}] 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 Personality User and Candidate passwords.%%
At line 149 changed 2 lines
!Resetting [{$applicationname}] User Passwords
[{$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.
!Resetting Personality User Passwords
Personality user passwords can be reset by security administrators through either the [IMRU] screen or through the [IMUS Access|IMUS#Access] tab within the Personality Professional application. These functions should be highly secured.
At line 152 changed one line
;__Find Block__:The [{$applicationname}] user whose password is to be changed must be located in the Find block on the top line.
;__Find Block__:The Personality user whose password is to be changed must be located in the Find block on the top line.
At line 161 changed one line
Self Service PIN numbers can be reset by security administrators through either [IMRE] or through the [IEID Self Service Access|IEID#SelfServiceAccessTab] tab within the [{$applicationname}] 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 [IEID Self Service Access|IEID#SelfServiceAccessTab] tab within the Personality Professional application. Access can be restricted to specific personnel records in both of these functions by setting up appropriate security rights.
At line 168 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 [{$applicationname}] 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 Personality User and Candidate passwords.%%
At line 173 changed one line
Candidate passwords can be reset by security administrators through either the [IRPIN] or through the [IRCA|IRCA#AssessmentsTab] Assessments tab within the [{$applicationname}] Professional application.
Candidate passwords can be reset by security administrators through either the [IRPIN] or through the [IRCA|IRCA#AssessmentsTab] Assessments tab within the Personality Professional application.
At line 183 changed one line
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.
Many different types of users use the Personality system – Personality Professional users, Self Service users and Candidates. All of these different types of users are referred to as “accessors” of the system. Personality uses a consistent approach for managing all accessors of the system.
At line 194 changed 2 lines
Each type of [{$applicationname}] user has a specific way of being authorized to access the system.
*[{$applicationname}] users are created and authorized through [IMUS].
Each type of Personality user has a specific way of being authorized to access the system.
*Personality 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 [{$applicationname}].
Below is a description of each of the different ways users can be authorized in Personality.
At line 202 changed 2 lines
!Authorizing [{$applicationname}] Users
[{$applicationname}] users are maintained by security administrators through the [IMUS] within the [{$applicationname}] 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 Personality Users
Personality users are maintained by security administrators through the [IMUS] within the Personality 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 212 changed one line
;[Access Tab]:This section contains the access information that is used by [{$applicationname}]. Refer to the [Common Accessor Information|USER PASSWORDS#CommonAccessorInformation] section for a detailed description.
;[Access Tab|]:This section contains the access information that is used by Personality. Refer to the [Common Accessor Information|USER PASSWORDS#CommonAccessorInformation] section for a detailed description.
At line 216 changed one line
Self Service users are maintained by a security administrator through the [IEID Self Service Access|IEID#SelfServiceAccessTab] tab within the [{$applicationname}] Professional application.
Self Service users are maintained by a security administrator through the [IEID Self Service Access|IEID#SelfServiceAccessTab] tab within the Personality Professional application.
At line 231 changed one line
Candidate access information is viewed and maintained by a security administrator through the [IRCA Self Service Access|IRCA#SelfServiceAccessTab] tab within the [{$applicationname}] Professional application.
Candidate access information is viewed and maintained by a security administrator through the [IRCA Self Service Access|IRCA#SelfServiceAccessTab] tab within the Personality Professional application.
At line 261 changed one line
Security administrators establish their own rules for system access by type of user. [{$applicationname}] offers many techniques for restricting access:
Security administrators establish their own rules for system access by type of user. Personality offers many techniques for restricting access:
At line 279 changed 2 lines
![{$applicationname}] System Access Rules
All access rules in [{$applicationname}] are defined by accessor type on [IMAR]. Access rules do not have to be set up in advance. They are created automatically during the first login if they do not already exist. However, the automatically generated access rules have no restrictions.
!Personality System Access Rules
All access rules in Personality are defined by accessor type on [IMAR]. Access rules do not have to be set up in advance. They are created automatically during the first login if they do not already exist. However, the automatically generated access rules have no restrictions.
At line 284 changed one line
[{$applicationname}]’s login and password verification techniques are all implemented within the application software and are not dependent on the database engine. The access rules no longer come from Oracle Profiles. Oracle Profiles should no longer be used in the [{$applicationname}] environment.
Personality’s login and password verification techniques are all implemented within the application software and are not dependent on the database engine. The access rules no longer come from Oracle Profiles. Oracle Profiles should no longer be used in the Personality environment.
At line 286 changed one line
Oracle Profiles should no longer be used in the [{$applicationname}] environment.
Oracle Profiles should no longer be used in the Personality environment.
At line 288 changed one line
[{$applicationname}] users are synchronized with the Oracle database users. When a user is created through [IMUS], an Oracle user is also created in the database. When a user’s password is changed in [{$applicationname}], it is also changed at the database level. Self Service users and Candidates are not identified as individual users at the database level.
Personality users are synchronized with the Oracle database users. When a user is created through [IMUS], an Oracle user is also created in the database. When a user’s password is changed in Personality, it is also changed at the database level. Self Service users and Candidates are not identified as individual users at the database level.
At line 292 changed one line
;[Validation Method| ]:Validation method is a mandatory field that identifies whether the new [{$applicationname}] password facility is being used and it identifies the algorithm used for encrypting the passwords.\\The allowed values are based on the fixed lexicon [X_VALIDATION_METHOD]:
;[Validation Method| ]:Validation method is a mandatory field that identifies whether the new Personality password facility is being used and it identifies the algorithm used for encrypting the passwords.\\The allowed values are based on the fixed lexicon [X_VALIDATION_METHOD]:
This page (revision-39) was last changed on 26-Nov-2021 10:22 by jaikenTop