This project was bootstrapped with Create React App.

Available Scripts

In the project directory, you can run:

npm start

Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.

The page will reload if you make edits.
You will also see any lint errors in the console.

npm test

Launches the test runner in the interactive watch mode.
See the section about running tests for more information.

npm run build

Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.

The build is minified and the filenames include the hashes.
Your app is ready to be deployed!

See the section about deployment for more information.

npm run eject

Note: this is a one-way operation. Once you eject, you can’t go back!

If you aren’t satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.

Instead, it will copy all the configuration files and the transitive dependencies (Webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.

You don’t have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.

Learn More

You can learn more in the Create React App documentation.

To learn React, check out the React documentation.

Create Postgresql user and database

• This will prompt you for the password to use

createuser --pwprompt aliasmgr

• Create the database

createdb -O aliasmgr aliasmanager

• Now you're ready to run the SQL creation script.

psql -U aliasmgr -d aliasmanager -a -f scripts/create.sql

API Endpoints

• /auth - POST { username: string, password: encoded-string }
  • return { userid, type, displayname, mailbox } AND set cookie
• /whoami - GET
  • return { userid, type, displayname, mailbox }
  • or 401
• /aliases - GET (?userid=id)
  • return { aliases: [ { address, status, createdby: { displayname }, createdate, note, isGroup }, ... ]
  • or 401 if not auth'd or 403 not admin
• /alias - POST { address, (note), action={add, update, disable} }
  • return 200 or 400
  • return 403 if address already exists
• /user - POST { type, displayname, mailbox, action={add, update} }
  • return 200
  • or 403 if not admin and adding user OR changing type on update
• /groupaliases - GET
  • return { "address": [ { userid, displayname, mailbox }, ... ], ...] }
  • or 403 if not admin
• /groupalias - POST { address, (note), (userid), action={add, update, disable} }
  • return 200
  • or 403 if not admin

Building and running the Java service

• Install the Bazel build tool brew install bazel
• Build the service jar bazel build QcEmailAliasService_deploy.jar
• Run the Java service java -jar bazel-bin/QcEmailAliasService_deploy.jar
• The Java service listens on port 8888 by default