Home

Results 91 - 100 of 22,657 for password. Search took 2.837 seconds.  
Sort by date/Sort by relevance
DRAFT ANNEX 11 TO THE TIR CONVENTION
There seems to be a requirement for authentication for electronic declarations in all countries and this is mostly done by “usernames and passwords” and/or “Public Key Infrastructure (PKI) electronic signature”. (...) ECE/TRANS/WP.30/2018/3 5 28 4 0 Always In some cases No 18 2 2 16 1 Usernames and passwords Symmetric KA SMS PKI Other 30 4 Yes No Question 2 (i) Does information/data submitted electronically (such as advance cargo information) need to be authenticated? (...) (ii) Please select the method or methods used by customs in your country for the authentication of the person sending electronic information (you can select more than one): (a) Usernames and Passwords; (b) Symmetric key authentication; (c) SMS based; (d) Public Key Infrastructure (PKI) electronic signature; (e) Other.
Language:English
Score: 861996.2 - https://daccess-ods.un.org/acc...=ECE/TRANS/WP.30/2018/3&Lang=E
Data Source: ods
FileAttributes ::= SEQUENCE { pathname Pathname-Attribute OPTIONAL , permitted-actions [1] Permitted-Actions-Attribute OPTIONAL , storage-account [3] Account-Attribute OPTIONAL , date-and-time-of-creation [4] Date-and-Time-Attribute OPTIONAL , date-and-time-of-last-modification [5] Date-and-Time-Attribute OPTIONAL , date-and-time-of-last-read-access [6] Date-and-Time-Attribute OPTIONAL , date-and-time-of-last-attribute-modification [7] Date-and-Time-Attribute OPTIONAL , identity-of-creator [8] User-Identity-Attribute OPTIONAL , identity-of-last-modifier [9] User-Identity-Attribute OPTIONAL , identity-of-last-reader [10] User-Identity-Attribute OPTIONAL , identity-of-last-attribute-modifier [11] User-Identity-Attribute OPTIONAL , object-availability [12] Object-Availability-Attribute OPTIONAL , object-size [13] Object-Size-Attribute OPTIONAL , future-object-size [14] Object-Size-Attribute OPTIONAL , access-control [15] Access-Control-Attribute OPTIONAL , legal-qualifications [16] Legal-Qualification-Attribute OPTIONAL , private-use [17] Private-Use-Attribute OPTIONAL , attribute-extensions [22] Attribute-Extensions OPTIONAL } Pathname-Attribute ::= CHOICE { incomplete-pathname [0] Pathname , complete-pathname [23] Pathname } Account-Attribute ::= CHOICE { no-value-available [0] NULL , -- Indicates partial support of this attribute actual-values Account } Account ::= GraphicString User-Identity-Attribute ::= CHOICE { no-value-available [0] NULL , -- Indicates partial support of this attribute. actual-values User-Identity } User-Identity ::= GraphicString Access-Control-Attribute ::= CHOICE { no-value-available [0] NULL , -- Indicates partial support of this attribute. actual-values [1] SET OF Access-Control-Element } -- The semantics of this attribute are described in ISO 8571-2 Access-Control-Element ::= SEQUENCE { action-list [0] Access-Request , concurrency-access [1] Concurrency-Access OPTIONAL , identity [2] User-Identity OPTIONAL , passwords [3] Access-Passwords OPTIONAL , location [4] Application-Entity-Title OPTIONAL } Access-Request ::= BIT STRING { read(0), insert(1), replace(2), extend(3), erase(4), read-attribute(5), change-attribute(6), delete-object(7)} Access-Passwords ::= SEQUENCE { read-password [0] Password , insert-password [1] Password , replace-password [2] Password , extend-password [3] Password , erase-password [4] Password , read-attribute-password [5] Password , change-attribute-password [6] Password , delete-password [7] Password , pass-passwords [8] Pass-Passwords , link-password [9] Password } Password ::= CHOICE { graphic-string GraphicString , octet-string OCTET STRING } Pass-Passwords ::= SEQUENCE OF Password Application-Entity-Title ::= SEQUENCE { ap-title AP-title , ae-qualifier AE-qualifier } END -- of IPMSFileTransferBodyPartType -- Generated by Asnp, the ASN.1 pretty-printer of France Telecom R&D
Language:English
Score: 860262.3 - https://www.itu.int/wftp3/Publ...SFileTransferBodyPartType.html
Data Source: un
Multiple authentication factors provide stronger identity assurance. 4-6 December Atlanta, Georgia, USA Password Authenticated Key Exchange PAKE - Standardized in ITU-T Rec. X.1035 and in ISO/IEC 11770-4 User establishes an Account and a Password on a server To login, Password is used to create a Key that encrypts a server challenge The encrypted challenge is sent to the server with an unencrypted Account Server receives encrypted challenge and Account locates user Password Server Password creates Key, decrypts challenge to authenticate user Server encrypts a response to challenge for user to mutually authenticate X.1035 can be extended to support multi-factor user authentication, by adding biometric and possession factors to the encrypted server challenge 4-6 December Atlanta, Georgia, USA What about people who can’t use passwords? Passwords are needed to operate PAKE, but they can come from many sources:  Traditionally, passwords come from keyboard, keypad, or touch screen entry   Biometric sensors can sometimes collect two authentication factors at once  Model-based sensor devices can map their results to password strings An obvious example of passwords from biometric sensors is recorded voice data Speech Recognition can extract a password from voice data Speaker Recognition can use voice data for biometric matching 4-6 December Atlanta, Georgia, USA Something-You-Know & Something-You-Are 4-6 December Atlanta, Georgia, USA Modeled sensor data mapped to passwords Hand Sign Password Substitution String R'W]$Pq57]mbTkG7j+$Uqe3#kbCf $ZkQB[ax<)p4D#QsWK}um<~k3D% K9hWFDeLG8,“O)hLNSaCF#<`A!
Language:English
Score: 858908.2 - https://www.itu.int/en/ITU-T/a...tions/S7.1_Phillip_Griffin.pdf
Data Source: un
In this case, log on through the classic method: enter the email address with which you subscribed to the list as a login and your list password in the 'Password' field. If you do not remember your list password, click on 'Lost password?'. Then enter your email address and password. Shortly afterward you will receive an email with a validation link. (...) Then you will be able to choose your password. Remember: the list password is a special password you will only use for the mailing list service.
Language:English
Score: 855769.7 - https://www.itu.int/ml/lists/help/user-authweb.html
Data Source: un
GE.12-21034 Econo
This operation was essential for the creation of the user profile and password that enabled access to the system. Each user was also assigned a profile which allowed him/her to see only the functions within their remit. For security reason the password was sent to the email address entered during registration and had to be changed when accessing the system for the first time. The new password is recorded in the system using encryption.
Language:English
Score: 855074.9 - daccess-ods.un.org/acce...DS=ECE/CES/GE.41/2012/7&Lang=E
Data Source: ods
For User name: enter the UserName that has been provided to you or Username@icao.int For the Password: enter the password you use to login to your work computer then click Sign in. Figure 2 3 Change Your PasswordChange Your PasswordChange Your PasswordChange Your Password If you need to change your password, you can do so from within OWA. 1. Navigate to the upper-right hand corner, click Options then select Change Your Password as shown in Figure 3. Figure 3 2. Enter your current password in the Current password: field and type your new password in the New password: and Confirm new password: fields.
Language:English
Score: 853707.3 - https://www.icao.int/Meetings/a39/Documents/LogInOutOWA.pdf
Data Source: un
F-READ-ATTRIB-response ::= SEQUENCE { action-result Action-Result DEFAULT success, attributes Read-Attributes OPTIONAL , -- Password values within the access control tan not be read by means -- of the read attribute action. (...) Zero indicates beginning of file; point after -- last checkpoint indicates end of file last-transfer-end-read-request [9] IMPLICIT INTEGER OPTIONAL , last-transfer-end-write-request [10] IMPLICIT INTEGER OPTIONAL } F-LOCATE-request ::= SEQUENCE { file-access-data-unit-identity FADU-Identity , fadu-lock FADU-Lock OPTIONAL } F-LOCATE-response ::= SEQUENCE { action-result Action-Result DEFAULT success, file-access-data-unit-identity FADU-Identity OPTIONAL , diagnostic Diagnostic OPTIONAL } F-ERASE-request ::= SEQUENCE {file-access-data-unit-identity FADU-Identity } F-ERASE-response ::= SEQUENCE { action-result Action-Result DEFAULT success, diagnostic Diagnostic OPTIONAL } Bulk-Data-PDU ::= CHOICE { f-read-request [32] IMPLICIT F-READ-request , f-write-request [33] IMPLICIT F-WRITE-request , -- There is no F-DATA FPDU, the contents of a file -- are transferred in a different presentation context -- and there is therefore no need to define the types -- of file contents in the FTAM PCI abstract Syntax. -- File contents data are carried in values of the -- data type Data-Element as defined in ISO 8571-2. f-data-end-request [34] IMPLICIT F-DATA-END-request , f-transfer-end-request [35] IMPLICIT F-TRANSFER-END-request , f-transfer-end-response [36] IMPLICIT F-TRANSFER-END-response , f-cancel-request [37] IMPLICIT F-CANCEL-request , f-cancel-response [38] IMPLICIT F-CANCEL-response , -- There is no F-CHECK PDU. f-restart-request [39] IMPLICIT F-RESTART-request , f-restart-response [40] IMPLICIT F-RESTART-response } F-READ-request ::= SEQUENCE { file-access-data-unit-identity FADU-Identity , access-context Access-Context , fadu-lock FADU-Lock OPTIONAL , -- The following is conditional on the negotiation of consecutive of concurrent access. transfer-number [0] IMPLICIT INTEGER OPTIONAL } F-WRITE-request ::= SEQUENCE { file-access-data-unit-Operation [0] IMPLICIT INTEGER {insert(0), replace(1), extend(2)}, file-access-data-unit-identity FADU-Identity , fadu-lock FADU-Lock OPTIONAL , -- The following is conditional on the negotiation of consecutive or concurrent access. transfer-number [1] IMPLICIT INTEGER OPTIONAL } F-DATA-END-request ::= SEQUENCE { action-result Action-Result DEFAULT success, diagnostic Diagnostic OPTIONAL } F-TRANSFER-END-request ::= SEQUENCE { shared-ASE-information Shared-ASE-Information OPTIONAL , -- The following are conditional on the negotiation of consecutive or concurrent access. request-type Request-Type OPTIONAL , transfer-number [0] IMPLICIT INTEGER OPTIONAL , last-transfer-end-read-response [1] IMPLICIT INTEGER OPTIONAL , last-transfer-end-write-response [2] IMPLICIT INTEGER OPTIONAL } F-TRANSFER-END-response ::= SEQUENCE { action-result Action-Result DEFAULT success, shared-ASE-information Shared-ASE-Information OPTIONAL , diagnostic Diagnostic OPTIONAL , -- The following are conditional on the negotiation of consecutive or concurrent access. request-type Request-Type OPTIONAL , transfer-number [0] IMPLICIT INTEGER OPTIONAL } F-CANCEL-request ::= SEQUENCE { action-result Action-Result DEFAULT success, shared-ASE-information Shared-ASE-Information OPTIONAL , diagnostic Diagnostic OPTIONAL , -- The following are conditional on the negotiation of consecutive or concurrent access. request-type Request-Type , transfer-number [0] IMPLICIT INTEGER OPTIONAL , last-transfer-end-read-request [1] IMPLICIT INTEGER OPTIONAL , last-transfer-end-read-response [2] IMPLICIT INTEGER OPTIONAL , last-transfer-end-write-request [3] IMPLICIT INTEGER OPTIONAL , last-transfer-end-write-response [4] IMPLICIT INTEGER OPTIONAL } F-CANCEL-response ::= SEQUENCE { action-result Action-Result DEFAULT success, shared-ASE-information Shared-ASE-Information OPTIONAL , diagnostic Diagnostic OPTIONAL , -- The following are conditional on the negotiation of consecutive or concurrent access. request-type Request-Type OPTIONAL , transfer-number [0] IMPLICIT INTEGER OPTIONAL , last-transfer-end-read-request [1] IMPLICIT INTEGER OPTIONAL , last-transfer-end-read-response [2] IMPLICIT INTEGER OPTIONAL , last-transfer-end-write-request [3] IMPLICIT INTEGER OPTIONAL , last-transfer-end-write-response [4] IMPLICIT INTEGER OPTIONAL } F-CHECK-request ::= SEQUENCE { checkpoint-identifier [0] IMPLICIT INTEGER , transfer-number [1] IMPLICIT INTEGER } F-CHECK-response ::= SEQUENCE { checkpoint-identifier [0] IMPLICIT INTEGER , transfer-number [1] IMPLICIT INTEGER } F-RESTART-request ::= SEQUENCE { checkpoint-identifier [0] IMPLICIT INTEGER , -- The following are conditional on the negotiation of consecutive or concurrent access. request-type Request-Type OPTIONAL , transfer-number [1] IMPLICIT INTEGER , last-transfer-end-read-request [2] IMPLICIT INTEGER OPTIONAL , last-transfer-end-read-response [3] IMPLICIT INTEGER OPTIONAL , last-transfer-end-write-request [4] IMPLICIT INTEGER OPTIONAL , last-transfer-end-write-response [5] IMPLICIT INTEGER OPTIONAL } F-RESTART-response ::= SEQUENCE { checkpoint-identifier [0] IMPLICIT INTEGER , -- The following are conditional on the negotiation of consecutive or concurrent access. request-type Request-Type OPTIONAL , transfer-number [1] IMPLICIT INTEGER , last-transfer-end-read-request [2] IMPLICIT INTEGER OPTIONAL , last-transfer-end-read-response [3] IMPLICIT INTEGER OPTIONAL , last-transfer-end-write-request [4] IMPLICIT INTEGER OPTIONAL , last-transfer-end-write-response [5] IMPLICIT INTEGER OPTIONAL } Degree-Of-Overlap ::= [ APPLICATION 30] IMPLICIT INTEGER { normal(0), consecutive(1), concurrent(2)} Request-Type ::= [ APPLICATION 31] IMPLICIT INTEGER {read(0), write(1)} Abstract-Syntax-Name ::= [ APPLICATION 0] IMPLICIT OBJECT IDENTIFIER Access-Context ::= [ APPLICATION 1] IMPLICIT SEQUENCE { access-context [0] IMPLICIT INTEGER {hierarchical-all-data-units(0), --HA-- hierarchical-no-data-units(1), --HN-- flat-all-data-units(2), --FA-- flat-one-level-data-unit(3), --FL-- flat-Single-data-unit(4), --FS-- unstructured-all-data-units(5), --UA-- unstructured-Single-data-unit(6)}, --US level-number [1] IMPLICIT INTEGER OPTIONAL } -- Present if and only if flat-one-level-data-units -- (access context FL) is selected. -- As defined in ISO 8571-2. Access-Passwords ::= [ APPLICATION 2] IMPLICIT SEQUENCE { read-password [0] Password , insert-password [1] Password , replace-password [2] Password , extend-password [3] Password , erase-password [4] Password , read-attribute-password [5] Password , change-attribute-password [6] Password , delete-password [7] Password , pass-passwords [8] IMPLICIT Pass-Passwords OPTIONAL , link-password [9] Password OPTIONAL } -- The pass-passwords and the link-password must be included in the -- access-passwords if and only if the limited-filestore-management -- or the Object-manipulation or the group-manipulation functional -- units are available. (...) Path-Access-Passwords ::= [ APPLICATION 27] IMPLICIT SEQUENCE OF SEQUENCE {read-password [0] IMPLICIT Password , insert-password [1] IMPLICIT Password , replace-password [2] IMPLICIT Password , extend-password [3] IMPLICIT Password , erase-password [4] IMPLICIT Password , read-attribute-password [5] IMPLICIT Password , change-attribute-password [6] IMPLICIT Password , delete-password [7] IMPLICIT Password , pass-passwords [8] IMPLICIT Pass-Passwords , link-password [9] IMPLICIT Password } -- There is a one-to-one correspondence between the elements of -- Path-Access-Passwords and the non-terminal elements sf the -- specified Pathname.
Language:English
Score: 851768.9 - https://www.itu.int/wftp3/Publ.../8571-4/1988/ISO8571-FTAM.html
Data Source: un
F-READ-ATTRIB-response ::= SEQUENCE { action-result Action-Result DEFAULT success, attributes Read-Attributes OPTIONAL, -- Password values within the access control tan not be read by means -- of the read attribute action. (...) Zero indicates beginning of file; point after -- last checkpoint indicates end of file last-transfer-end-read-request [9] IMPLICIT INTEGER OPTIONAL, last-transfer-end-write-request [10] IMPLICIT INTEGER OPTIONAL } F-LOCATE-request ::= SEQUENCE { file-access-data-unit-identity FADU-Identity, fadu-lock FADU-Lock OPTIONAL } F-LOCATE-response ::= SEQUENCE { action-result Action-Result DEFAULT success, file-access-data-unit-identity FADU-Identity OPTIONAL, diagnostic Diagnostic OPTIONAL } F-ERASE-request ::= SEQUENCE {file-access-data-unit-identity FADU-Identity } F-ERASE-response ::= SEQUENCE { action-result Action-Result DEFAULT success, diagnostic Diagnostic OPTIONAL } Bulk-Data-PDU ::= CHOICE { f-read-request [32] IMPLICIT F-READ-request, f-write-request [33] IMPLICIT F-WRITE-request, -- There is no F-DATA FPDU, the contents of a file -- are transferred in a different presentation context -- and there is therefore no need to define the types -- of file contents in the FTAM PCI abstract Syntax. -- File contents data are carried in values of the -- data type Data-Element as defined in ISO 8571-2. f-data-end-request [34] IMPLICIT F-DATA-END-request, f-transfer-end-request [35] IMPLICIT F-TRANSFER-END-request, f-transfer-end-response [36] IMPLICIT F-TRANSFER-END-response, f-cancel-request [37] IMPLICIT F-CANCEL-request, f-cancel-response [38] IMPLICIT F-CANCEL-response, -- There is no F-CHECK PDU. f-restart-request [39] IMPLICIT F-RESTART-request, f-restart-response [40] IMPLICIT F-RESTART-response } F-READ-request ::= SEQUENCE { file-access-data-unit-identity FADU-Identity, access-context Access-Context, fadu-lock FADU-Lock OPTIONAL, -- The following is conditional on the negotiation of consecutive of concurrent access. transfer-number [0] IMPLICIT INTEGER OPTIONAL } F-WRITE-request ::= SEQUENCE { file-access-data-unit-Operation [0] IMPLICIT INTEGER {insert(0), replace(1), extend(2)}, file-access-data-unit-identity FADU-Identity, fadu-lock FADU-Lock OPTIONAL, -- The following is conditional on the negotiation of consecutive or concurrent access. transfer-number [1] IMPLICIT INTEGER OPTIONAL } F-DATA-END-request ::= SEQUENCE { action-result Action-Result DEFAULT success, diagnostic Diagnostic OPTIONAL } F-TRANSFER-END-request ::= SEQUENCE { shared-ASE-information Shared-ASE-Information OPTIONAL, -- The following are conditional on the negotiation of consecutive or concurrent access. request-type Request-Type OPTIONAL, transfer-number [0] IMPLICIT INTEGER OPTIONAL, last-transfer-end-read-response [1] IMPLICIT INTEGER OPTIONAL, last-transfer-end-write-response [2] IMPLICIT INTEGER OPTIONAL } F-TRANSFER-END-response ::= SEQUENCE { action-result Action-Result DEFAULT success, shared-ASE-information Shared-ASE-Information OPTIONAL, diagnostic Diagnostic OPTIONAL, -- The following are conditional on the negotiation of consecutive or concurrent access. request-type Request-Type OPTIONAL, transfer-number [0] IMPLICIT INTEGER OPTIONAL } F-CANCEL-request ::= SEQUENCE { action-result Action-Result DEFAULT success, shared-ASE-information Shared-ASE-Information OPTIONAL, diagnostic Diagnostic OPTIONAL, -- The following are conditional on the negotiation of consecutive or concurrent access. request-type Request-Type, transfer-number [0] IMPLICIT INTEGER OPTIONAL, last-transfer-end-read-request [1] IMPLICIT INTEGER OPTIONAL, last-transfer-end-read-response [2] IMPLICIT INTEGER OPTIONAL, last-transfer-end-write-request [3] IMPLICIT INTEGER OPTIONAL, last-transfer-end-write-response [4] IMPLICIT INTEGER OPTIONAL } F-CANCEL-response ::= SEQUENCE { action-result Action-Result DEFAULT success, shared-ASE-information Shared-ASE-Information OPTIONAL, diagnostic Diagnostic OPTIONAL, -- The following are conditional on the negotiation of consecutive or concurrent access. request-type Request-Type OPTIONAL, transfer-number [0] IMPLICIT INTEGER OPTIONAL, last-transfer-end-read-request [1] IMPLICIT INTEGER OPTIONAL, last-transfer-end-read-response [2] IMPLICIT INTEGER OPTIONAL, last-transfer-end-write-request [3] IMPLICIT INTEGER OPTIONAL, last-transfer-end-write-response [4] IMPLICIT INTEGER OPTIONAL } F-CHECK-request ::= SEQUENCE { checkpoint-identifier [0] IMPLICIT INTEGER, transfer-number [1] IMPLICIT INTEGER } F-CHECK-response ::= SEQUENCE { checkpoint-identifier [0] IMPLICIT INTEGER, transfer-number [1] IMPLICIT INTEGER } F-RESTART-request ::= SEQUENCE { checkpoint-identifier [0] IMPLICIT INTEGER, -- The following are conditional on the negotiation of consecutive or concurrent access. request-type Request-Type OPTIONAL, transfer-number [1] IMPLICIT INTEGER, last-transfer-end-read-request [2] IMPLICIT INTEGER OPTIONAL, last-transfer-end-read-response [3] IMPLICIT INTEGER OPTIONAL, last-transfer-end-write-request [4] IMPLICIT INTEGER OPTIONAL, last-transfer-end-write-response [5] IMPLICIT INTEGER OPTIONAL } F-RESTART-response ::= SEQUENCE { checkpoint-identifier [0] IMPLICIT INTEGER, -- The following are conditional on the negotiation of consecutive or concurrent access. request-type Request-Type OPTIONAL, transfer-number [1] IMPLICIT INTEGER, last-transfer-end-read-request [2] IMPLICIT INTEGER OPTIONAL, last-transfer-end-read-response [3] IMPLICIT INTEGER OPTIONAL, last-transfer-end-write-request [4] IMPLICIT INTEGER OPTIONAL, last-transfer-end-write-response [5] IMPLICIT INTEGER OPTIONAL } Degree-Of-Overlap ::= [APPLICATION 30] IMPLICIT INTEGER { normal(0), consecutive(1), concurrent(2)} Request-Type ::= [APPLICATION 31] IMPLICIT INTEGER {read(0), write(1)} Abstract-Syntax-Name ::= [APPLICATION 0] IMPLICIT OBJECT IDENTIFIER Access-Context ::= [APPLICATION 1] IMPLICIT SEQUENCE { access-context [0] IMPLICIT INTEGER {hierarchical-all-data-units(0),--HA-- hierarchical-no-data-units(1),--HN-- flat-all-data-units(2),--FA-- flat-one-level-data-unit(3),--FL-- flat-Single-data-unit(4),--FS-- unstructured-all-data-units(5),--UA-- unstructured-Single-data-unit(6)}, --US level-number [1] IMPLICIT INTEGER OPTIONAL } -- Present if and only if flat-one-level-data-units -- (access context FL) is selected. -- As defined in ISO 8571-2. Access-Passwords ::= [APPLICATION 2] IMPLICIT SEQUENCE { read-password [0] Password, insert-password [1] Password, replace-password [2] Password, extend-password [3] Password, erase-password [4] Password, read-attribute-password [5] Password, change-attribute-password [6] Password, delete-password [7] Password, pass-passwords [8] IMPLICIT Pass-Passwords OPTIONAL, link-password [9] Password OPTIONAL } -- The pass-passwords and the link-password must be included in the -- access-passwords if and only if the limited-filestore-management -- or the Object-manipulation or the group-manipulation functional -- units are available. (...) Path-Access-Passwords ::= [APPLICATION 27] IMPLICIT SEQUENCE OF SEQUENCE {read-password [0] Password, insert-password [1] Password, replace-password [2] Password, extend-password [3] Password, erase-password [4] Password, read-attribute-password [5] Password, change-attribute-password [6] Password, delete-password [7] Password, pass-passwords [8] IMPLICIT Pass-Passwords, link-password [9] Password} -- There is a one-to-one correspondence between the elements of -- Path-Access-Passwords and the non-terminal elements sf the -- specified Pathname.
Language:English
Score: 851768.9 - https://www.itu.int/wftp3/Publ...o/8571-4/1988/ISO8571-FTAM.asn
Data Source: un
OSLA (Office of Staff Legal Assistance) User Manual Created Date: 09th December, 2016 Version: 2.0 User Manual Version: 2.0 Page 2 of 12 Table of Contents (Re-generate the TOC after modifications to the document) Contents Table of Contents (Re-generate the TOC after modifications to the document) ............................................................................................................................ 2 1 Introduction ............................................................................................................................................................................................................................. 3 2 Getting Started ......................................................................................................................................................................................................................... 3 2.1 Login Form ....................................................................................................................................................................................................................... 3 2.2 Sign Up ............................................................................................................................................................................................................................. 3 2.3 Forgot Password .............................................................................................................................................................................................................. 4 2.4 Dashboard ........................................................................................................................................................................................................................ 5 2.5 Change Password ............................................................................................................................................................................................................. 6 2.6 Sign Out ............................................................................................................................................................................................................................ 6 3 Create New Cases .................................................................................................................................................................................................................... 7 3.1 Personal Details ............................................................................................................................................................................................................... 8 3.2 Case Details: You will have to enter case related & employment related details in this section ................................................................................... 8 3.3 Chronology: ...................................................................................................................................................................................................................... 9 3.4 Version History: .............................................................................................................................................................................................................. 11 User Manual Version: 2.0 Page 3 of 12 1 Introduction The purpose of this document is to capture the existing workflow and process, followed from start to finish by all the members of the OSLA staff. 2 Getting Started Please Note: UN Logo has been changed for the application. (...) If you are an existing user enter the Username/Email ID in the respective text box highlighted and the password in the text box after it 3. Click on Sign In button after entering your credentials Enter Password Enter User name / Email ID User Manual Version: 2.0 Page 4 of 12 2.2 Sign Up 1) If you are a new user, then click on the Sign Up link highlighted above, which will take you to the registration page as shown below 2) Enter appropriate Username and Password, First Name, Last Name & Email ID in the respective fields as shown below 3) Then enter the characters displayed in the CAPTCHA image and click on “Create User” button to register 4) You will receive an email notification with the password for you to login 5) Enter the same password along with user name while trying to login 2.3 Forgot Password 1) If you have forgotten your password, then click on the “forgot password” link highlighted in the following image to set a new password Sign Up Enter User Enter First name Enter Last name Enter Email ID Enter Characters Enter new password Re-enter password User Manual Version: 2.0 Page 5 of 12 2) You will be redirected to a new page where you need to enter Username / Email ID as shown below and click on Submit. 3) Once you enter the correct Username / Email ID you will get the following message 4) Click on Continue to go back to the Login Form 5) You will receive an email notification with your new password 6) Enter the same password along with you registered Username / Email ID in the Login Form to login to the Dashboard 2.4 Dashboard The dashboard gives you an overview of your drafts & cases 1) User Settings: You can access settings like About User, Sign Out & Change Password from highlighted drop down link 2) Navigation Pane: You can create a new case or access the dashboard from the Navigation pane 3) All Cases: You can choose if you would like to view a list of your Drafts or Cases or Requests raised on behalf of other Staff Members, Enter User name / Email ID Continue 1 2 3 4 5 4 6 5 User Manual Version: 2.0 Page 6 of 12 selecting the appropriate option. (...) You can View/Edit an individual record from here too 5) Pages Navigation: You can navigate to Previous & Next pages from here 6) Entries per page: You can select number of records per page view from here 2.5 Change Password 1) Click on your drop down link present in the top right corner of the dashboard 2) Click on the option of Change Password from the drop down 3) A new page with new Password options will open as shown below 2.6 Sign Out 1) Click on your drop down link present in the top right corner of the dashboard 2) Click on the “Sign Out” option from the drop down as highlighted above 3) Upon successful sign out you will be redirected to the login page 4) Enter your Current Password & your New Password in all the respective fields as highlighted above and click on “change password” button Current Password New Password Re-Enter New Password User Manual Version: 2.0 Page 7 of 12 3 Create New Cases Click on “+ Create New Request” link present in the left hand side Navigation pane, which will open the following screen.
Language:English
Score: 849869.5 - https://www.un.org/en/internal...dfs/OSLAWRequestAssistance.pdf
Data Source: un
After these steps are completed and the request reviewed, you will receive ICAO Portal Access Instructions. 4 III. Reset password All ICAO Net account passwords will expire within six months. All users are informed automatically by e-mail seven days before their passwords expire. 1. Upon receiving email notification of pending password expiry, users are expected to log on to the site and click on the Profile link to change their password. These instructions are provided in the e-mail notification. 2. If the password has already expired, or if a user has forgotten his or her password please follow the instructions below. a) Navigate to http://portal.icao.int b) At the login page, click on the ‘Cannot Login’ link c) Enter your email address or your username and click on submit. d) Enter the answer to your hint to receive a new password. e) The new password will be sent to your email address ------------------ http://portal.icao.int/
Language:English
Score: 848686.6 - https://www.icao.int/coscap/AW...al%20Access%20Instructions.pdf
Data Source: un