Training features
Spider now manages training specific rights and features specifically added to enhance the trainings experience and help the trainer do his job whatever the system.
Origin
When designing the exercises for the user training, I designed whisperers, team and users that needed to be created.
At first, I thought of providing a script to the trainers to create the relevant data... But I was faced against the packaging challenge of this script, especially on systems where the trainer won't have administrator rights. It is best if he does not, right?
And it is best if he does not need a specific system too =)
So in the end, I figured out it was best to include the training features inside the system straight !
What training features?
All features are reusing a lot of existing Spider features and API.
So they were quite fast to build :)
Specific rights
Trainers have to be given 'userTrainer' rights. And without any access to anything else, they may perform their training. As in a sandbox.
Trainee creation
Trainers may create trainees user account on the UI.
Trainee are given a random name and linked password and are given to real trainees. The latter may then change, as it suits them all user fields, like:
- password
- names
This automatic creation has linked the accounts to the trainer, so he may:
- Impersonate them for support
- Delete them at any time to recreate account or clear once training is over
The creation also automatically created two whisperers for the training exercises needs.
Training team creation
Trainers may create training teams on the UI.
The training teams has got automatically associated settings and whisperers, as the solution of exercises. And it is ready to be shared, with token, and explicit name.
Trainee account removal
Trainees may be deleted from the UI, and their whisperers will be removed as well.
Training team deletion
Training team may be deleted from the UI and its whisperers will be removed as well.
Bonus
It also allowed fixing a couple of bugs in UI and monitoring ;)