Repository navigation
feat(auth): strengthen account security and add memory deletion - #585
Merged
Merged
Conversation
Use salted versioned scrypt hashes while verifying existing SHA-256 records and upgrading them only after successful login. Keep valid logins working when migration persistence fails. Use hash verification for PIN changes and preserve existing sessions, temporary PIN flows and admin recovery. Document the rollback limit for older binaries that cannot read migrated hashes.
Add opt-in account PIN-to-password enrollment and optional verified passkeys. Preserve migrated PIN credentials and legacy single-user authentication, while disabling redundant Server PIN controls and login in account mode. Persist expiring hashed sessions, account/IP login limits and explicit HTTPS proxy trust. Keep device management inside personal settings with accurate activity metadata and row-local sign-out confirmation. Validate with 86 targeted regression tests and shared-browser checks.
Remember successfully authenticated accounts with server-side browser hints and an opaque cookie, without granting authentication authority. Add progressive sign-in with Clay branding, responsive input cards, password and PIN transitions, and existing passkey and email options.
Treat absent server configuration as empty when determining account policy. Update the onboarding integration check for the new sign-in page heading.
Add owner-bound revision-checked deletion with an atomic tombstone and linked report disposition. Keep deleted knowledge out of active retrieval and prevent stale curation from restoring it. Provide a Me deletion dialog with pending and error handling, refresh other tabs, and preserve the existing Project Log deletion action.
Contributor
|
This issue has been resolved in version 5.2.0-beta.1 (main). To update, run: -- Clay Deploy Bot Build anything, with anyone, in one place. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes
Account-enabled installations can use passwords/passphrases and passkeys, with a compatible transition from existing account PINs. Single-user and Server PIN access remain supported. Server administration controls and personal security settings are separated; signed-in devices can be reviewed and revoked within User Settings.
Sign-in now starts with an account chooser and remembers accounts on this browser after successful authentication. Remembered identities never grant access without authentication. The page uses Clay's loading-screen branding and direct sign-in headings.
Owners can delete saved Me knowledge from its detail view. Deleted entries leave active retrieval and future context; the append-only record retains history. Existing owner-only Project Log deletion remains available in log details.
Security and compatibility
Validation