Results for “auth”

Validate a sign-up form (email, password, name) in one call, with a message per field, in the browser and the API alike.

Check a login form (email, password): the normalised email to look up, or a message for each field to fix.

Issue an API's HS256 access token, read one from an Authorization header, and refuse revoked or superseded ones.

Check a change-password form: current password given and correct, new one meeting the policy and different.

Sign, verify and decode HS256 JSON Web Tokens (RFC 7519): signature, algorithm and exp/nbf/iat checked with leeway.

The token from an HTTP Authorization header of the form "Bearer <token>" (RFC 6750), or null if it has none.

Check a new password against a named policy (NIST SP 800-63B-4 by default): length, common passwords, name and email.

Hash a password for storage as pbkdf2_sha256$iterations$salt$hash, verify one in constant time, and spot weak hashes.

Allow a login attempt or lock the account out, from its recent failed attempts, with the seconds until it may retry.

Trim an email address and lower-case its domain for storage and lookup, or null if it is not a plausible address.

A password input with a Show/Hide button and an optional live checklist of a password policy (GOV.UK password input).

PBKDF2 with HMAC-SHA256 (RFC 8018): derive a key from a password and salt, slowly, fast enough for a login request.

HMAC-SHA256 of a message under a secret key (RFC 2104, RFC 4231), in pure code that also runs in the browser.

The SHA-256 digest of a byte string (FIPS 180-4), in pure code that also runs in the browser.

Bytes to lowercase hexadecimal text and back (RFC 4648 base16), strictly, identically in every language.

A form's state as a pure reducer: values, touched fields, validator errors and the submit, for useReducer.

Is this a plausible email address? A documented, pragmatic subset of RFC 5322, not the full grammar.

Check an IBAN against the ISO 13616 mod-97-10 checksum and the registered length for its country.

Check a 20-character Legal Entity Identifier against its ISO 17442 / ISO 7064 MOD 97-10 check digits.

Check a double-entry journal: debits equal credits, no zero or two-sided lines, one currency, well-formed account codes.

Check a digit string against the Luhn mod-10 checksum used by payment cards and many identifiers.

Initials from a personal name for avatars and signatures: "Jean-Paul Sartre" is "JPS".

Check the format of a SWIFT/BIC code (8 or 11 characters) and split it into its parts.

Check an HMRC Unique Taxpayer Reference's modulus 11 check digit, accepting the K and spacing people type.

Compare two byte strings in time that does not depend on where they differ, for checking MACs and hashes.

Check a 17-character vehicle identification number and its check digit; enforced for North American VINs.

Validate one network inventory entry: name, host, ports, optional MAC and subnet, with every problem listed.

Age at policy inception and the rating band it falls in, from a table of age bands.

Check a host name against RFC 1123 and RFC 952 label rules and length limits, and normalise it.

Customer lifetime value, LTV to CAC ratio and CAC payback months from ARPA, gross margin, churn and CAC.

Fuzzy-match a name against existing clients and parties for a conflict check: normalised, token-sorted Jaro-Winkler.

Trial balance from journal lines: debit or credit balance per account, and proof that debits equal credits.

Retention held and released on a construction valuation: full rate, half at practical completion, none at the end.

The to-do item type (Todo, TodoDraft, Recurrence) and its validators, with a message per field.

Check a UK VAT registration number against HMRC's mod-97 checksum, including the post-2010 9755 variant.

Share a tips pool (tronc) between staff by hours worked, points, or hours times points, exactly to the penny.