I'm having problems too with the identification process. Yes, and I have read comments about the extreme slowness of replies from the support team, with some people waiting 3 or more days for a response.
At first, whenever I clicked 'identity', a window appeared stating, 'internal server error'. Besides this, I felt uncomfortable about having my real name displayed in this forum so I viewed a message from Coinbase on how to change it. To conclude, can an employee of Coinbase kindly resolve my issues.
Select your encryption type from the "Network Authentication" and "Data Encryption" drop downs.
I'm trying to understand how to make sure that a logged on user's account is still "valid" (where valid means for example not locked out, not deleted) I've set up an identity provider using Identity Server v3. What's working so far: This works fine, but I want some kind of hourly validation that the user is still "valid" from the identity servers perspective.
On the RP-side, I'm using Use Open Id Connect Authentication to install the Open Id Connect Authentication Middleware in the Owin pipeline.
Authentication is the process by which an application confirms user identity.
Applications have traditionally persisted identity through session cookies, relying on session IDs stored server-side.