+
+ | Which private data do we store at "swift" and why? |
+
+
+ | What do we save? |
+ Why? |
+
+
+ |
+ User accounts: The user accounts contain the real name (z.B. Joe Doe),
+ email, the Id number of the associated network (e.g. VATSIM), country of the user,
+ user name (user account).
+
+ With each login we log date and time, origin of login (e.g. via browser, the swift client),
+ furthermore creation time of the user account.
+
+ Hint: User account in swift are normally subject of self administation, so the user can
+ change the profile.
+ |
+
+ The Email address is required for notifcation such as forgotten password.
+ The unique id is used for SSO (single sign on) with third party authentication systems (e.g. VATSIM)
+ |
+
+
+ |
+ Change history: We store a change history who and when change something.
+ Overall picture: We deal with flight simulation data,
+ no high security or critical data.
+ |
+
+ We store the change history in case we need to crosscheck and verify information.
+ |
+
+
+ | What data are stored in the developer area of phabricator? |
+
+
+ | What do we save? |
+ Why? |
+
+
+ |
+ User accounts consists of real name (e.g. Joe Doe), email, the id number of the associated
+ network (e.g. VATSIM), user name (user account). Passwords are not saved in clear text
+ and admistered by the user himself.
+
+ Hint: Users can change their profile (see below)
+ |
+
+ Needed for user administration and change history.
+ |
+
+
+ |
+ Change history: All changes of tasks, bug reports, software artifacts are logged.
+ (who and when was the changed applied?).
+ |
+
+ In a software project we need to know, who and why a software omponent has been changed.
+ |
+
+
+ |
+ Version control: We use git as version control system.
+ The commit history shows who has changed which part in swift and when this has happened.
+ |
+
+ Further details can be found in the git doscumentation.
+ |
+
+
+ | Where can I see/verify my data? |
+
+
+ | Self administration |
+ Why? |
+
+
+ |
+ Your master data (profile) in datastore and in Phabricator
+ can be self administered. For VATSIM a simplified Single-Sign-On has been established,
+ sharring the VATSIM data with swift (the password is NOT transferred).
+ |
+
+ |
+
+
+ | Recommendations |
+
+
+ | email and passwords |
+ Why? |
+
+
+ |
+ If possible use an individual email address for swift only.
+ Please use safe passwords, but none you use otherwise.
+ |
+
+ In case of any security breach you can lock/dismiss this individual email
+ and password and no other accounts/systems can be compromissed.
+ |
+
+
+
+