Update staging

[timiajayi]

​

Description

​

Related Issue (Link to Github issue)

​

Motivation and Context

​

How Has This Been Tested?

​

Screenshots (if appropriate - Postman, etc):

​

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
  ​

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

[gitguardian]

⚠️ GitGuardian has uncovered 20 secrets 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 secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
13348443	Triggered	Generic High Entropy Secret	c459649	tests/Unit/RegistrationTest.php	View secret
13348443	Triggered	Generic High Entropy Secret	c459649	tests/Unit/RegistrationTest.php	View secret
13348443	Triggered	Generic High Entropy Secret	7ce357b	tests/Unit/RegistrationTest.php	View secret
13348443	Triggered	Generic High Entropy Secret	7ce357b	tests/Unit/RegistrationTest.php	View secret
13348443	Triggered	Generic High Entropy Secret	a6ef177	tests/Unit/RegistrationTest.php	View secret
13348443	Triggered	Generic High Entropy Secret	18eceed	tests/Unit/RegistrationTest.php	View secret
13348443	Triggered	Generic High Entropy Secret	18eceed	tests/Unit/RegistrationTest.php	View secret
13348443	Triggered	Generic High Entropy Secret	a6ef177	tests/Unit/RegistrationTest.php	View secret
13348444	Triggered	Generic Password	c459649	tests/Feature/RoleCreationTest.php	View secret
13348444	Triggered	Generic Password	a6ef177	tests/Feature/RoleCreationTest.php	View secret
13348444	Triggered	Generic Password	265261e	tests/Feature/RoleCreationTest.php	View secret
13348444	Triggered	Generic Password	d28fbe0	tests/Feature/RoleCreationTest.php	View secret
13348460	Triggered	Generic High Entropy Secret	c459649	.env.example	View secret
13348460	Triggered	Generic High Entropy Secret	a6ef177	.env.example	View secret
13348460	Triggered	Generic High Entropy Secret	df081a2	.env.example	View secret
13348460	Triggered	Generic High Entropy Secret	aa5dbe6	.env.example	View secret
13348460	Triggered	Generic High Entropy Secret	93c0af2	.env.example	View secret
13348460	Triggered	Generic High Entropy Secret	df081a2	.env.example	View secret
13348460	Triggered	Generic High Entropy Secret	d28fbe0	.env.example	View secret
13348460	Triggered	Generic High Entropy Secret	a224f07	.env.example	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 secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
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.}