timuntersberger/keycape

Documentation https://keycape.netlify.com

keycape's Issues

Improve diffing of config.yaml

Currently we try to create every entity defined and log when a unique value already exists.

But what if you only changed the scopes of an account. Currently it doesnt update the entity in the db.

Marketing frontpage ideas

Frontpage needs three marketing points.
my ideas:

• one config file
• open source
• docker

Add session based authentication

Invalidation

Support either accesstoken or refreshtoken invalidation (most likely by using a blacklist in redis)

Error Codes

Currently the only way of knowing what error got returned is by comparing the error message. This is very inefficient for the user and error prone.

Create a unique error code for each error message that gets propagated back to the user.

Don't forget to document all of the codes!

Update dev enironment

change from using ts-node to a proper build process

Config

Add following validations before persisting the entities:

• Name has to be unique
• Referncing a role or privilege that doesn't exist is not possible

Migrations Production

The mikro orm migrator up function always tries to do every migration.

Somehow only do the migrations once.

Validate API input

Support forgot password

Use extra scopes provided in config file

scope values are validated but not used.

Finish CRUD endpoints

• Account
  • create one
  • get one
  • get all
  • update one
  • delete one
  • get role
  • get oauth2connections
• Role
  • create one
  • get one
  • get all
  • update one
  • delete one
  • get privileges
  • add privilege
  • remove privilege
• Privilege
  • create one
  • get one
  • get all
  • update one
  • delete one

Privilege -> Scope

Rename Privilege to Scope (To align more to the oauth2 spec)

rename config.yaml -> keycape.yaml

Add error message when config is missing

Refresh Token Lifetime

Currently the refresh token is hard coded to 7d.
There is no way to change this as a user of keycape without forking the repo.

Make it configurable

Forgot Password Token Livetime

Currently the forgot password token is hard coded to 10 minutes.
There is no way to change this as a user of keycape without forking the repo.

Make it configurable

OAuth2: handle duplicate providerId signups

Currently when someone uses an already registered provider account to signup the program just crashes.

Access token payload

Think about the current accesstoken payload. Maybe we should only send the id of the account instead of the whole account.

Connect existing account

Currently it is only possible to connect an account with a provider by signing in with that provider.

It would be awesome if you could add a provider to an existing account.

Improve Error Messages

Currently not all errors are handled probably or propagated back to the user.

Access Token Lifetime

Currently the access token is hard coded to 15 minutes.
There is no way to change this as a user of keycape without forking the repo.

Make it configurable

Write documentation

• - connect google
  • - create a google application
  • - find google id and secret
• - connect github
  • - create a github application
  • - find github id and secret
• - describe api