Don't let the client be responsible for giving the timestamp, let it just pass the number of minutes the secret should remain active. This avoids wasting any of that time during the creation of that secret.
Currently, there's also a bug with the TimeLimitation constraint, because we were supposed to be expecting a timestamp, not the lifetime of the secret in minutes. This change will fix that bug
Currently there are only unit tests implemented. Integration tests will allow for more thorough testing of different layers altogether, from client to database.
Currently there is no way for the project to automatically delete expired secrets. The functionality is implemented but relies on an external tool such as a cron job. The project should handle it itself and efficiently.