feat: keycloak clientId and client secret manage on the user table - Githubissues

credebl / platform

Open source, Open standards based Decentralised Identity & Verifiable Credentials Platform

Apache License 2.0

31 stars 13 forks source link

feat: keycloak clientId and client secret manage on the user table #780

Closed KulkarniShashank closed 2 weeks ago

KulkarniShashank commented 2 weeks ago

What

Adding new columns to the user table for storing Keycloak clientId and client secret.
Implementing the logic to update and retrieve these values when creating or updating a user.
Modifying the necessary services and controllers to handle the new fields.

Why

Managing Keycloak clientId and client secret directly on the user table is necessary to: Simplify the integration between our application and Keycloak by having the authentication details directly associated with the user.

How

Service and Controller Updates:

Update user creation and update services to include ClientId and Client Secret fields.
Modify the relevant controllers to accept and process these fields in user-related requests.

sonarcloud[bot] commented 2 weeks ago

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud