You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Implement the new register-client flow with a goal to support SCRAM authentication on the client portal.
We have to:
Fetch the parameters required to generate storedKey and serverKey on frontend, i.e. iterationCount and salt (that can be achieved by creating a new endpoint register-client-precheck on backend to return this data given client username)
generate saltedPassword, storedKey and serverKey on frontend as per the sequence diagrams
Send client-specific data (username, backend_uri, redirect_uri, etc) as well as hashes that now represent user's password (i.e. storedKey and serverKey) to the backend
On the backend, persist this data into the clients table
Acceptance criteria:
Put all the changes necessary to implement this functionality under version v2 (i.e. new API endpoints, API endpoint modifications, as well as new methods)
The client is successfully able to register using the new flow
storedKey and serverKey are persisted into the clients table instead of the password
Implementation is fully covered with unit tests
The text was updated successfully, but these errors were encountered:
Implement the new register-client flow with a goal to support SCRAM authentication on the client portal.
We have to:
storedKey
andserverKey
on frontend, i.e.iterationCount
andsalt
(that can be achieved by creating a new endpointregister-client-precheck
on backend to return this data given clientusername
)saltedPassword
,storedKey
andserverKey
on frontend as per the sequence diagramsusername
,backend_uri
,redirect_uri
, etc) as well as hashes that now represent user's password (i.e.storedKey
andserverKey
) to the backendclients
tableAcceptance criteria:
v2
(i.e. new API endpoints, API endpoint modifications, as well as new methods)storedKey
andserverKey
are persisted into theclients
table instead of thepassword
The text was updated successfully, but these errors were encountered: