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 7ccc7b0d17
Remove crypto code and update code to point at Iolaus.Crypto instead
22 hours ago
app Remove crypto code and update code to point at Iolaus.Crypto instead 22 hours ago
config Add application-wide configuration and crypto configuration 4 months ago
schema Start adding types needed to create accounts and make them admins 22 hours ago
scripts Connect to a database and migrate it 4 months ago
src/Sthenauth Remove crypto code and update code to point at Iolaus.Crypto instead 22 hours ago
test Remove crypto code and update code to point at Iolaus.Crypto instead 22 hours ago
.envrc Remove crypto code and update code to point at Iolaus.Crypto instead 22 hours ago
.gitignore Remove crypto code and update code to point at Iolaus.Crypto instead 22 hours ago
CHANGES.md Implement secure password hashing for storing passwords in a database 5 months ago
LICENSE Initial import 5 months ago
README.md Add database tables for accounts and emails, refactor some crypto stuff 4 months ago
Setup.hs Implement secure password hashing for storing passwords in a database 5 months ago
default.nix Remove crypto code and update code to point at Iolaus.Crypto instead 22 hours ago
shell.nix Remove crypto code and update code to point at Iolaus.Crypto instead 22 hours ago
sthenauth.cabal Remove crypto code and update code to point at Iolaus.Crypto instead 22 hours ago

README.md

Sthenauth: Never Write Authentication Code Again!

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 with support for AAL1, AAL2, and AAL3
    • Replay resistant (multi-factor authentication)
    • Verifier-impersonation resistant (anti-phishing)
    • Verifier-compromise resistance (client certificates)
    • 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:

    • OAuth2 Generic
    • Google
    • GitHub
    • 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.