Système permettant de renouveler token d’API RDV-S [GEN-1763]

[leo-naeka]

ℹ️ NE PAS RELIRE LE PREMIER COMMIT

🤔 Pourquoi ?

Les API RDV-I et RDV-S partagent la même base d'utilisateurs et les mêmes informations d'identification.

Leurs tokens sont émis pour une durée de 24h et chaque renouvellement invalide les tokens antérieurs.

🍰 Comment ?

Les informations d'identification sont mises en cache et automatiquement actualisées selon le besoin.

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
13074360	Triggered	Generic High Entropy Secret	541ccff	itou/utils/mocks/rdv_insertion.py	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[xavfernandez]

Et est-ce qu'on ne souhaiterait pas un petit test ? Je viens de voir qu'il y avait un 3ème commit 😫