Single Sign On (SSO) Authentication
- Jeff Duke
Target release | 5.0.0 |
|---|---|
Epic |
|
Document status | DRAFT |
Document owner | @ mention owner |
Designer | @ designer |
Tech lead | @ lead |
Technical writers | @ writers |
QA |
|
Objective
Add support for SSO integration, like CAS, SAML, OAuth.
Requirements
Requirement | User Story | Importance | Jira Issue | Notes |
|---|---|---|---|---|
Install SSO Plugins and configure. |
| HIGH |
|
|
Update user profile screen to allow for setting temporary password. Add separate local password expiration. |
| HIGH |
|
|
Add barcode printing and reading functionality for local passwords. |
| HIGH |
|
|
User interaction and design
In addition to implementing the SSO authentication integration, we also need to update the in-app or over the shoulder authentication that is currently available. Prescription approval and issue actions and Document verification both require a secondary username and password authentication. Need to find an alternate process for the SSO type of secondary authentication that does not take over or interrupt the current Spring Session.
Potentially using Locally encrypted password (DAO) with an automatic short timeframe expiration. For example, allowing for a user to create a daily password, once authenticated into VetView with SSO. This password would only be usable inside of VetView for the secondary authentication actions. The user could print a barcode that could be used to speed up the process for users like pharmacist approving scripts.