Keys for Controlled Release

[morganduverney]

BEFORE SUBMITTING AN ISSUE CHECK THE FOLLOWING:

• [x] I checked existing issues.
• [x] This is not a support question (which can be answered on Slack).
• [x] This issue is for the API / Game Engine code base (not Web Client, Lambda, or Bots)

FEATURE REQUEST

A feature request constitutes any feature not currently supported by the API / Game Engine that does not fall under a Game Play Request.

- Describe the feature you would like to see. Create a key that would allow exclusive access to wombats.io

- Why you believe this would improve the quality of the Wombat's API / Game Engine. We need a way to prevent carte blanche access to wombats.io. A way to do this would be to share keys with selected users that allows access.

- Provide details on expected behavior. Need to discuss what this will look like.

[emilyseibert]

What are keys

• unique
• user defined "uva hackathon" not guid
• contain metadata: a description of why the key has been created, event description
• configurable limit on # of users that can use the key
• expiration date

Flow

• On /beta?beta_key=xyz
• Authorize user through github and update them in db
• Check to see if user is in beta
• If not in beta, check to see if key is valid (valid if max uses haven't been reach, exp date has not been reach)
• update key stats and update user to beta status
• redirect to client

[emilyseibert]

Will need to be able to accept a new key name and create in db

[oconn]

Acceptance Criteria: Users cannot log in without using an access key. If an access key is used they can log in as normal

[morganduverney]

At a high-level, this appears to be working as expected. I'd love to test to make sure the limit works as expected, i.e. when 100 people have used the key, we get an error message (or something) that the key is invalid. @oconn what do you think?

[morganduverney]

Tested and determined that I can log in with an expired access key. Could also log in using an access key that already had max number of users. Kicking back to fix validation.

[morganduverney]

Woooo this is fixed! Closing.