https://github.com/xeoneux/key_server

Rails implementation of a simple key server challenge.
https://github.com/xeoneux/key_server

activejob keyserver rails ruby ruby-on-rails

Last synced: 5 days ago
JSON representation

Rails implementation of a simple key server challenge.

• Host: GitHub
• URL: https://github.com/xeoneux/key_server
• Owner: xeoneux
• Created: 2019-02-23T05:49:22.000Z (almost 6 years ago)
• Default Branch: master
• Last Pushed: 2023-01-19T11:53:26.000Z (almost 2 years ago)
• Last Synced: 2024-10-30T00:40:07.392Z (about 2 months ago)
• Topics: activejob, keyserver, rails, ruby, ruby-on-rails
• Language: Ruby
• Homepage:
• Size: 43.9 KB
• Stars: 2
• Watchers: 2
• Forks: 0
• Open Issues: 8
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
Write a server which can generate random api keys, assign them for usage and release them after sometime. Following endpoints should be available on the server to interact with it.

1. There should be one endpoint to generate keys.

2. There should be an endpoint to get an available key. On hitting this endpoint server should serve a random key which is not already being used. This key should be blocked and should not be served again by E2 while it is in this state. If no eligible key is available then it should serve 404.

3. There should be an endpoint to unblock a key. Unblocked keys can be served via E2 again.

4. There should be an endpoint to delete a key. Deleted keys should be purged.

5. All keys are to be kept alive by clients calling this endpoint every 5 minutes. If a particular key has not received a keep alive in last five minutes then it should be deleted and never used again.

Apart from these endpoints, following rules should be enforced:

1. All blocked keys should get released automatically within 60 secs if E3 is not called.

No endpoint call should result in an iteration of whole set of keys i.e. no endpoint request should be O(n). They should either be O(lg n) or O(1).

Also add RSpecs (Unit tests) along with the code.