2 ms·
> > Are there any techniques for identity providers to authenticate people without storing or transmitting the users password to them? > This question doesn't
by tsimionescu 4y ago
> > Are there any techniques for identity providers to authenticate people without storing or transmitting the users password to them?
> This question doesn't quite compute for me, do you mean provisioning as opposed to authenticating? There's no reason an identity provider would need to send a user's password to the user when trying to authenticate that user.
I believe "them" here referred to "identity providers" - that is, can an identity provider authenticate a person without that person sending their password to the identity provider?
The response to that is yes, though they are not widely used - WebAuthn is a standard though that covers this - though in such a system there simply is no password.
The idea that you would have a password but not send it to the identity provider makes no sense: the whole purpose of the identity provider is to recognize you. When using an IdP, you are protecting your password from the final website who only gets to see what details you allow the identity provider to share with them. If you trust the website more than the identity provider, you shouldn't be using the identity provider at all.
- blincoln 4y ago> The idea that you would have a password but not send it to the identity provider makes no sense It's possible to prove to a remote system that one knows their own password without sending the password (or an equivalent, like NTLM hashes). Secure Remote Password protocol (SRP)[1] is one specific implementation. [1] https://en.wikipedia.org/wiki/Secure_Remote_Password_protocol https://en.wikipedia.org/wiki/Secure_Remote_Password_protoco...