RESTAPI:Validity of Verifications: Unterschied zwischen den Versionen
imported>Frorathm Keine Bearbeitungszusammenfassung |
Keine Bearbeitungszusammenfassung |
||
| Zeile 1: | Zeile 1: | ||
In order to increase the safety of created verification tokens, Cryptshare administrators are able to set-up validity terms for verifications. Please refer to the chapter [[CSSCurrent en:Verification|Verification]] where maximum and idle validity terms are discussed. | In order to increase the safety of created '''verification tokens''', Cryptshare administrators are able to set-up validity terms for verifications. Please refer to the chapter [[CSSCurrent en:Verification|Verification]] where maximum and idle validity terms are discussed. | ||
The validity of a verification token can be checked when the verification token is sent in the '''X-CS-VerificationToken''' header to the following endpoint, together with the used client id ('''X-CS-ClientId''' header) used in the request of the verification token and the respective email address in the request path: | |||
GET https://<your-url>/api/users/<email-address>/verification | GET https://<your-url>/api/users/<email-address>/verification | ||
Using this endpoint you get the information if your verification is (still) valid and if it is valid, until when it is valid. The '''validUntil''' value denotes the earlier date of maximum validity date (if configued) and idle validity date. | Using this endpoint you get the information if your verification is (still) valid and if it is valid, until when it is valid. The '''validUntil''' value denotes the earlier date of maximum validity date (if configued) and idle validity date. | ||
Aktuelle Version vom 13. Juni 2024, 07:34 Uhr
In order to increase the safety of created verification tokens, Cryptshare administrators are able to set-up validity terms for verifications. Please refer to the chapter Verification where maximum and idle validity terms are discussed.
The validity of a verification token can be checked when the verification token is sent in the X-CS-VerificationToken header to the following endpoint, together with the used client id (X-CS-ClientId header) used in the request of the verification token and the respective email address in the request path:
GET https://<your-url>/api/users/<email-address>/verification
Using this endpoint you get the information if your verification is (still) valid and if it is valid, until when it is valid. The validUntil value denotes the earlier date of maximum validity date (if configued) and idle validity date.