Skip to content

Latest commit

 

History

History
38 lines (35 loc) · 2.81 KB

TODO.md

File metadata and controls

38 lines (35 loc) · 2.81 KB

Work to do

  • documentation
  • wrap at least /Trust and /Distrust in AuthZ
    • Probably also the PUT /Certificate and the POST /BatchJob
    • This means I'll need to make it either
      • use Krb5 for AuthN and then lookup the groups
        • And does this mean retrieving the PAC from an AD TGT, or making an LDAP lookup?
      • OR I will need to make it require a JWT from OAuth/OpenID Connect, and then check the roles
        • learning to OAuth-ify an app fills me with ph33r and intimidation
    • either way, it sounds difficult and intimidatiing
  • switch from SQLite3 to instead a real database, like SQL Svr, Oracle, PostGres
  • externalize configuration
    • This will be particularly important for things like database connection information, AuthZ allowed roles/groups, AuthZ configuration (server, relying-party secret, etc)
    • The pattern we will use is
      • have the application retrieve configurable parms from environment variabled
        • if the environment variable is not set, set a sane default in code
        • if the value of the environment variable is nonsensical, set a sane default in code
      • have the operator of the application pass the environment variable in, using "--env" command-line parm to the "docker run" command docker run -d --env 'TRUSTMANAGER_DATABASE_URL'='sqlite:///certificates.db' -p 5100:5100 trustmanager-api
  • add logging of all subroutine invocations, as well as all input passed in, whether as URL parameters or in the body of a message
    • When there is an error (such as an HTTP 500), log enough context that I can make sense of what happened
    • When there is a database write, log previous value, new value, and what made the change
    • probably want to send all logged messages via SYSLOG, with configurable SYSLOG server and configurable SYSLOG facility
      • It will probably always just be one of the LOCAL0-LOCAL7 facilities, since the built-in facilities don't really apply, and feel like a throwback to the mid-nineties.

Completed

  • GUI
    • Decision: Native WPF/WinForms in PowerShell, or web GUI
    • Decided a Web GUI for now. May make a native Windows GUI some other time
  • batch job for Windows truststore
    • I know you can distribute and manage truststore with Group Policy
    • I know you can distribute Group Policy in ADMX files, which are XML-encoded collections of GPOs
    • I need to see if I can figure out how to make an ADMX to distribute a GPO that manages trust, providing all the root CAs in the database maked trusted
  • Documentation how to consume/operationalize the truststores
  • instructions to run inside a WSGI server, instead of the built-in development webserver
    • It's now running under waitress.serve. That was easy.
  • Dockerfile to package the app + WSGI server + Python together