This repository has been archived by the owner on Dec 16, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1
Testing LocalEGA
Frédéric Haziza edited this page Oct 30, 2017
·
19 revisions
- User does not exist
- User does not have rights to access this Local EGA
- User authentication failed: password or ssh-key
- User authentication succeeds but user inbox not created: ssh/sftp access denied
- Database connection fails, so user information is not available
- User tries to login via something else than ssh/sftp
- User applies the wrong encryption protocol (ie not OpenPGP)
- User uses the wrong GPG key or sends it to the wrong LocalEGA
- Ingestion starts but inbox not created
- Ingestion starts but file not found in inbox
- File found but its checksum doesn't match with the supplied one
- File found but its checksum doesn't match with the companion file
- File found, no checksum supplied and no companion file
- File found, its checksum is correct but the GPG decryption fails (and why)
To be expanded. That item comprises many tests! eg Keyserver communication fails: Server down, SSL encryption channel is not set up... GPG key not found, GPG key not unlocked etc
- File found, its checkusum is valid, the GPG decryption succeed but the checksum of the decrypted doesn't match with the supplied one
- File found, its checkusum is valid, the GPG decryption succeed but the checksum of the decrypted doesn't match with the companion file
- File found, ...., but re-encryption fails (and why)
To be expanded. This item comprises many tests! eg key not found
- Re-encryption failure due shortage in the staging area
To be expanded. This item comprises many tests! eg disk full, or mount failed, ...
- Moving to staging area failed
Vault listener is down, vault disk is full, staging area mount failed, etc...
- Verification of the copied file in the vault failed
The file was not fully copied, so its checksum failed (calculated at the re-encryption step).
- Database connection failed, so information about the file is not available
- Everything works after a system reboot (manually or power outage)
- Some components are restarted (especially the database, but also the ingestion workers or the vault)
- Stress tests:
- ingesting a big file
- ingesting many files