Login and Password: Unterschied zwischen den Versionen

Aus Faces Dokumentation
Wechseln zu: Navigation, Suche
(General)
 
(11 dazwischenliegende Versionen von 3 Benutzern werden nicht angezeigt)
Zeile 1: Zeile 1:
 +
 
= General =
 
= General =
 
+
 
 
To join Umbrella Faces Suite, the following data are required:
 
To join Umbrella Faces Suite, the following data are required:
  
* User name (Benutzernamen)
+
*User name (Benutzername)  
* Password (Passwort)
+
*Password (Passwort)  
* Agency-Key
+
*Agency-Key (Agentur)
  
Those login data are allocated to a [[Profile Traveller|Traveller]], [[Profile Traveller#Declaration profile types "Arranger, Approver, Profile Manager"|Arranger]] , [[Profile Traveller#Declaration profile types "Arranger, Approver, Profile Manager"|Approver]] and [[Administrator|Administrator]].
+
Those login data are allocated to a [[Profile_Traveller|Traveller]], [[Profile_Traveller#Declaration_profile_types_"Arranger,_Approver,_Profile_Manager"|Arranger]] , [[Profile_Traveller#Declaration_profile_types_"Arranger,_Approver,_Profile_Manager"|Approver]] and [[Administrator|Administrator]].
  
 
= Procedures / Processes =
 
= Procedures / Processes =
Zeile 13: Zeile 14:
 
== Credentials ==
 
== Credentials ==
  
Credentials are sent via email.
+
Credentials are sent via email. Credentials can be sent by an arranger, approver, administrator or a profile manager and a supporter.
Credentials can be sent by an arranger, approver, administrator/profile manager and supporter.
+
 
 +
[[File:Credentials email.PNG|700px|Credentials email]]
  
[[Image:Credentials email.PNG|700px|Credentials email]]
 
  
 
== Login ==
 
== Login ==
  
The URL https://tenzing.umbrella.ch/faces/login can be entered with the obtained credentials.  
+
The URL [https://faces.umbrellanet.ch/faces/login https://faces.umbrellanet.ch/faces/login] can be accessed with the obtained credentials.
 +
 
 +
[[File:Faces Loginpage.PNG|Faces_Loginpage]]
 +
 
 +
 
  
[[Image:Login Page.PNG|700px|Login Page]]
+
[[Category:Seiten mit defekten Dateilinks]]
  
 
== Data protection / Privat policy ==
 
== Data protection / Privat policy ==
  
After initial entry, the data protection provisions must be accepted.
+
After the initial login, the data protection provisions have to be accepted.
 +
 
 +
[[File:Private policy.PNG|250px|private policyt]]
 +
 
 +
 
  
[[Image:private policy.PNG|250px|private policyt]]
 
  
 
== Password ==
 
== Password ==
  
=== Renewal Password ===
+
Passwords must be changed at least every 90 days.<br/> The password must have a minimum length of 8 characters.<br/> The password must contain upper and lower case letters, numbers and at least one special character.<br/> When changing the password none of the last 3 year stored passwords can be used.<br/> After 3 failed login attempts a user account is locked for 30 minutes or forget passwort function ca be used.<br/> After 15 minutes of inactivity, the password must be entered to reactivate the terminal / session.<br/> The maximum session time after which the user must log in again must not exceed 200 minutes.
 +
 
 +
=== Password renewal ===
  
 
The password must be renewed every 90 days.
 
The password must be renewed every 90 days.
 
The password must contain at least 8 characters, with a minimum of one digit and one letter.
 
  
 
=== New password request ===
 
=== New password request ===
  
If a user forgets his password, a new password can be requested.
+
If a user forgets their&nbsp;password, a new password can be requested.
 
 
 
 
[[Image:Passwort_vergessen1.PNG|250px|Passwort_vergessen1]]
 
  
 +
[[File:Passwort vergessen1.PNG|250px|Passwort_vergessen1]]
  
[[Image:new_password.PNG|250px|new_password]]
+
[[File:New password.PNG|250px|new_password]]
  
 
=== Change temporary password ===
 
=== Change temporary password ===
  
The first time you log in, the temporary password from the login email must be changed.
+
The first time you log in, the temporary password from the login email hast to be changed. The new password must conform to the password guideline requirements indicated above.
  
The password must contain at least 8 characters, with a minimum of one digit and one letter.
+
[[File:Change Password.PNG|250px|Change_Password]]
  
[[Image:Change Password.PNG|250px|Change_Password]]
+
&nbsp;
  
 
=== Password locked ===
 
=== Password locked ===
  
After three times a wrong password is entered, the user access is blocked for 10 minutes.
+
After a wrong password is entered three times, the user access is blocked for 10 minutes. A new password&nbsp;must be requested if the user wants to access Faces immediately.
For instant access a new password will need to be requested.
 
  
[[Image:PW_gesperrt.PNG|250px|PW_gesperrt]]
+
[[File:PW gesperrt.PNG|250px|PW_gesperrt]]
 +
 
 +
&nbsp;
  
 
=== Password including AeTM-Integration ===
 
=== Password including AeTM-Integration ===
  
When working with the AeTM-Integration (see [[Profile_Traveller#AeTM Integration|AeTM Integration]]), the Tenzing Faces credentials are not relevant. Therefore, the login works slightly different:
+
When working with the AeTM-Integration (see [[Profile_Traveller#AeTM_Integration|AeTM Integration]]), the Faces credentials are not relevant. Therefore, the login works slightly different:
* Tenzing Faces username and password are only displayed by creating new travellers (mandatory)
 
* To prevent that the AeTM password stored in Tenzing Faces is not different from that in AeTM, the [[CRS_Configuration#Community_Settings|Community Settings]] should be adjusted with 'Enable password expiration', so that AeTM passwords never expire. If this is not configured, the user will eventually be forced to set a new password directly in AeTM, while in Tenzing Faces then still the old password is stored.
 
  
* The AeTM-Integration will '''never''' check an expired password in Tenzing Faces.
+
*Faces username and password are only displayed by creating new travellers (mandatory)
 +
*To make sure that the AeTM password stored in Faces is the same as that in AeTM, the [[CRS_Configuration#Community_Settings|Community Settings]] should be adjusted with 'Enable password expiration', so that AeTM passwords never expires. If this is not configured, the user will eventually be forced to set a new password directly in AeTM, whereas&nbsp;in Faces the&nbsp;old password will still be saved.
 +
 
 +
*The AeTM-Integration&nbsp;'''never'''&nbsp;verifies&nbsp;if&nbsp;a password in Faces&nbsp; is expired or not and it does not realise either if it were.
  
 
== User rights ==
 
== User rights ==
  
 
{|
 
{|
! User level !! Own traveller profile || Edit self !! Edit other travellers !! Edit company !! Edit travel agency
 
 
|-
 
|-
| Traveller || yes || X || || ||
+
! User level
 +
! Own traveller profile
 +
! Edit self
 +
! Edit other travellers
 +
! Edit company
 +
! Edit travel agency
 
|-
 
|-
| Approver, Arranger || yes || X || Only assigned travelers || ||  
+
| Traveller
 +
| Yes
 +
| X
 +
| &nbsp;
 +
| &nbsp;
 +
| &nbsp;
 
|-
 
|-
| Company admin || no || X || All travelers in same company || some data ||  
+
| Approver, Arranger
 +
| Yes
 +
| X
 +
| Only assigned travellers
 +
| &nbsp;
 +
| &nbsp;
 
|-
 
|-
| Agency admin || no || X || All travelers || yes || some data
+
| Company admin
 +
| No
 +
| X
 +
| All travellers in same company
 +
| Only some of the data/ fields
 +
| &nbsp;
 +
|-
 +
| Agency admin
 +
| No
 +
| X
 +
| All travellers
 +
| yes
 +
| Only some of the data/ fields
 
|}
 
|}
 +
 +
[[Category:Seiten mit defekten Dateilinks]]

Aktuelle Version vom 18. Mai 2020, 10:06 Uhr

General

To join Umbrella Faces Suite, the following data are required:

  • User name (Benutzername)
  • Password (Passwort)
  • Agency-Key (Agentur)

Those login data are allocated to a Traveller, Arranger , Approver and Administrator.

Procedures / Processes

Credentials

Credentials are sent via email. Credentials can be sent by an arranger, approver, administrator or a profile manager and a supporter.

Credentials email


Login

The URL https://faces.umbrellanet.ch/faces/login can be accessed with the obtained credentials.

Faces_Loginpage

 

Data protection / Privat policy

After the initial login, the data protection provisions have to be accepted.

private policyt

 


Password

Passwords must be changed at least every 90 days.
The password must have a minimum length of 8 characters.
The password must contain upper and lower case letters, numbers and at least one special character.
When changing the password none of the last 3 year stored passwords can be used.
After 3 failed login attempts a user account is locked for 30 minutes or forget passwort function ca be used.
After 15 minutes of inactivity, the password must be entered to reactivate the terminal / session.
The maximum session time after which the user must log in again must not exceed 200 minutes.

Password renewal

The password must be renewed every 90 days.

New password request

If a user forgets their password, a new password can be requested.

Passwort_vergessen1

new_password

Change temporary password

The first time you log in, the temporary password from the login email hast to be changed. The new password must conform to the password guideline requirements indicated above.

Change_Password

 

Password locked

After a wrong password is entered three times, the user access is blocked for 10 minutes. A new password must be requested if the user wants to access Faces immediately.

PW_gesperrt

 

Password including AeTM-Integration

When working with the AeTM-Integration (see AeTM Integration), the Faces credentials are not relevant. Therefore, the login works slightly different:

  • Faces username and password are only displayed by creating new travellers (mandatory)
  • To make sure that the AeTM password stored in Faces is the same as that in AeTM, the Community Settings should be adjusted with 'Enable password expiration', so that AeTM passwords never expires. If this is not configured, the user will eventually be forced to set a new password directly in AeTM, whereas in Faces the old password will still be saved.
  • The AeTM-Integration never verifies if a password in Faces  is expired or not and it does not realise either if it were.

User rights

User level Own traveller profile Edit self Edit other travellers Edit company Edit travel agency
Traveller Yes X      
Approver, Arranger Yes X Only assigned travellers    
Company admin No X All travellers in same company Only some of the data/ fields  
Agency admin No X All travellers yes Only some of the data/ fields