Currently the backend does not create a unique hash for the signature verification challenge, it uses a static Test Hash defined in the Auth Controller and UI. This is not safe for obvious reasons. Please implement the InitChallenge() endpoint within the Auth Controller. See the InitChallengeResponse dto. Use in mem caching with the id to temporarily persist the hash
A/C
InitChallenge is Implemented on the backend.
If a ticket is not yet entered for the UI to remove the hard coded value and use the newly provided hash from this endpoint please enter it.
Currently the backend does not create a unique hash for the signature verification challenge, it uses a static Test Hash defined in the Auth Controller and UI. This is not safe for obvious reasons. Please implement the InitChallenge() endpoint within the Auth Controller. See the InitChallengeResponse dto. Use in mem caching with the id to temporarily persist the hash
A/C