Secure, highly performant authentication server written in Haskell.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Peter J. Jones 536e6b69de
Log in and out of local accounts, start using the event log
3 days ago
app Switch to Relude, clean up imports and language extensions 1 month ago
config Log in and out of local accounts, start using the event log 3 days ago
doc/images Tweaks to the README.md 1 month ago
schema Associate accounts and email addresses with sites 6 days ago
scripts Add database trigger to set the `updated_at' columns on UPDATE 4 weeks ago
src Log in and out of local accounts, start using the event log 3 days ago
test Switch to Relude, clean up imports and language extensions 1 month ago
ui Start building the Elm frontend 1 week ago
www Start building the Elm frontend 1 week ago
.envrc Port to latest version of iolaus-crypto, new keys container type `Keys' 1 month ago
.gitignore Start building the Elm frontend 1 week ago
.hlint.yaml Switch to Relude, clean up imports and language extensions 1 month ago
CHANGES.md Implement secure password hashing for storing passwords in a database 7 months ago
LICENSE Initial import 7 months ago
README.md Added type `Policy' and supporting types 4 weeks ago
Setup.hs Implement secure password hashing for storing passwords in a database 7 months ago
default.nix Log in and out of local accounts, start using the event log 3 days ago
shell.nix Remove crypto code and update code to point at Iolaus.Crypto instead 1 month ago
sthenauth.cabal Log in and out of local accounts, start using the event log 3 days ago

README.md

Sthenauth: Never Write Authentication Code Again!

Sthenauth

An authentication server that can be used by off-the-shelf and custom software without having to reinvent the wheel. In other words, don’t write your own authentication solution (you’ll probably get it wrong).

Status

This project is currently under heavy development. A stable release is forthcoming. Watch this space.

Features

  • Standards-compliant management of passwords and sessions

    • Conforms to NIST 800-63B
    • Support for Authenticator Assurance Levels:
      • AAL1: Basic authentication (most common)
      • AAL2: At least two factors of authentication
      • AAL3: Mandatory multi-factor with hardware devices
    • Secrets are safe even if someone has access to the database
    • Passwords are hashed with PBKDF2 (HMAC + SHA-3 512)
    • Automatic password re-hashing as needed
    • Unicode passwords are normalized (NFKC) then stored as UTF-8
    • Upgrade legacy password databases (bcrypt)
  • Protects personally identifiable information (PII)

    • Encrypted email addresses (with site-wide key)
    • Hashed email addresses (with salt) for deterministic lookup
  • Attack counter measures:

    • Real-time brute force detection
    • Slow attack responses without affecting real users
  • Auditing

    • Complete event log of all actions taken
    • Statistics transmitted to a time series database
  • Acts as a remote authentication provider:

  • Authenticate with external providers:

    • OIDC
    • SAML
    • LDAP
    • PAM
  • User interface:

    • Customize the UI so it matches your brand
    • Users can change and reset passwords
    • Administrator interface
  • Open and Free:

    • Open source, released under the Apache License.
    • Free, even for commercial use
    • Commercial support available

Goals

  • Secure by default.

    You shouldn’t have to be a security expert to install or use Sthenauth. As much as possible we try to make it impossible to install or configure Sthenauth in a way that would make it insecure.

Name

Sthenauth takes its name from the gorgon Stheno, the immortal sister of Medusa. The face of a gorgon was used in Ancient Greece as a way to ward off evil.