Question
Against the selected PocketBase version, can a Base collection safely receive a natively hashed password and validate it with Record.ValidatePassword without exposing plaintext or any token-issuing auth path, or must United use a dedicated non-interactive Auth collection with public authentication endpoints disabled?
Question
Against the selected PocketBase version, can a Base collection safely receive a natively hashed password and validate it with Record.ValidatePassword without exposing plaintext or any token-issuing auth path, or must United use a dedicated non-interactive Auth collection with public authentication endpoints disabled?