...
Variable | Description |
|---|---|
| The username of the authorized user. |
| The role of the user. |
| The hashed context of the session. This will be compared to a sent cookie. See the “Potential Vulnerabilities” section for more details. |
| (Built-in to JWT) The date the token was issued. Note that the date is the number of seconds since Jan 1 1970. This is the equivalent of the Javascript |
| The date the token expires. |
...
The method by which the token will be securely obtained by the Safe Places web app.
...
...
Scope
The Safe Places backend will not be handling the management of the user pool.
I.E. there will be no
/loginendpoint that accepts ausernameandpasswordand performs a local database lookup.
Token attainment will largely depend on the health authority. They may implement their own system for issuing JSON Web Token that we will have to adapt to.They may also control a separate user pool that the backend has to perform API calls on. This would mean issuing tokens would be within the Safe Places scope.To accommodate common methods of identity management, the Safe Places backend will enable compatibility with Lightweight Directory Access Protocol (LDAP) and/or Active Directory (AD).
SPL Web App sends the
usernameandpasswordto SPL Backend.SPL Backend uses DN resolution based on the sent username.
LDAP Server responds with the distinguished name (DN) of the user.
SPL Backend runs the
bindcommand to validate theDNandpassword.LDAP Server responds with either success or failure.
If successful, SPL Backend issues a JSON Web Token with appropriate permissions to the client.
| Gliffy | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Potential Vulnerabilities
...