Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow generating user API keys in selfhosted Polr #141

Closed
strugee opened this issue Feb 15, 2016 · 5 comments
Closed

Allow generating user API keys in selfhosted Polr #141

strugee opened this issue Feb 15, 2016 · 5 comments

Comments

@strugee
Copy link

strugee commented Feb 15, 2016

Currently if you're selfhosting Polr you need to manually insert API keys into the db. This kinda sucks.

I should be able to provide a username and password and get back usable API keys. Furthermore links generated using those keys should be associated with the correct user, and the user should be able to revoke API keys.

@cydrobolt
Copy link
Owner

This is available in 2.0. Admins can toggle the status of API keys for each user or choose to reset their keys. I'm planning to allow users to reset or toggle this on their own as well. The keys link the created links to the user who owns the keys.

They should be able to view these in their user panel.

I'm going to leave this ticket open until I add the option for users (non admin users) to toggle and view their own keys. :)

@strugee
Copy link
Author

strugee commented Feb 17, 2016

@cydrobolt great! Almost hate to ask, but any idea when 2.0 will be out?

@cydrobolt
Copy link
Owner

@strugee really soon (tm)

@cydrobolt
Copy link
Owner

Admins should now be able to assign, reset, and manage API keys.

We still need to implement key revocation from the user-side, and give admins the ability to change the quota from the admin panel.

@cydrobolt
Copy link
Owner

Closing in favour of #156

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants