User Tools
auth:ticket:userguide
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
auth:ticket:userguide [2017/11/15 16:20] florence [Credits] |
auth:ticket:userguide [2024/04/04 15:50] (current) |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | <html><!-- nomoodle --></html>{{ :logo-apl.png?nolink |}} <html><!-- /nomoodle --></html> | ||
| + | |||
| ===== Ticket based authentication : User guide===== | ===== Ticket based authentication : User guide===== | ||
| - | ===Ticket Direct Access (to Moodle) plugin=== | + | ===Ticket Direct Access (to Moodle) plugin introduction=== |
| Using a ticket based authentification is implicit: | Using a ticket based authentification is implicit: | ||
| Line 15: | Line 18: | ||
| ===Use Case=== | ===Use Case=== | ||
| - | Dans le cadre de l'utilisation de la boutique, dans le cadre d'une émission de notification de facture au client, le client peut revenir au cours support pour télécharger sa facture sans s'authentifier via le couple login/mot de passe. Le système génère un jeton d'accès crypté temporaire transmis pour une durée de validité temporaire dans le corps du mail émis. | + | When working with [[:local:shop|moode integrated shop]], when sending a quote or an invoice to the customer, the auth ticket is used to provide the purchaser a long term access ticket to upload his generated documents, whithout necessarily having to log in again in moodle. The acces point with embedded generated ticket will be part of the notification email. |
| - | :!: Cette porte d'entrée est potentiellement à utiliser en https pour éviter toute interception. | + | :!: The auth/ticket access point should e used in HTTPS to avoid any interception of ticket value. |
| <html><!-- nomoodle --></html> | <html><!-- nomoodle --></html> | ||
auth/ticket/userguide.1510759235.txt.gz · Last modified: 2024/04/04 15:50 (external edit)
