auth:chore - Keycloak decode token to get accountID.

[lucasbrunozup]

When the auth verify the user permission, the current code
called keycloak server for get accountID, and this can be
considered a DDos attack for keycloak.

I change the function for the decode the accessToken and
get the accountID from this.

Signed-off-by: lucas.bruno [email protected]

[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.

🔎 Details of the secret

Secret	Commit	Filename	Detected At
Generic High Entropy Secret	bbad3ba	auth/internal/services/authentication/keycloak/client/keycloak_test.go	12:45 January 12th, 2022	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 is an automated secrets detection service.We help developers and security teams secure the modern software development process.

 

Our GitHub checks need improvements? Share your feedbacks