Versions Compared
Version | Old Version 6 | New Version Current |
---|---|---|
Changes made by | ||
Saved on |
Key
- This line was added.
- This line was removed.
- Formatting was changed.


Implementation models
Table of Contents | ||||
---|---|---|---|---|
|
Model I
In this model, the BackOffice application is a typical server application that can access the AlisonServer service using a custom API-Key.
This API-Key is used to obtain the JWT token used by Alison Server to list the certificates and to request access to the private key of the certificate.


Model II
This implementation uses TadGateway to obtain the JWT token required for Alison Server to access the end user credential services.
In this case, the API-Key is stored in the TadGateway, and the user must provide his seatId and a captcha.

