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

Admin API Token Issue #95

Closed
mtanvir21 opened this issue Feb 2, 2015 · 3 comments
Closed

Admin API Token Issue #95

mtanvir21 opened this issue Feb 2, 2015 · 3 comments
Assignees
Labels
Milestone

Comments

@mtanvir21
Copy link

Hi, I've noticed that when you're on the Edit Admin page for the first admin account that was created, it doesn't show the admin API token. However, if you login with admin accounts that were created after the initial admin account this is not an issue. Any idea why this is happening?

@GUI
Copy link
Member

GUI commented Feb 3, 2015

The admin authentication tokens are only shown for your own admin account. So you must be logged in under an admin account to view its authentication token. Does that explain the behavior you're seeing? And does that make sense? The reasoning behind this is that you should only have access to your own admin token, and not tokens for other admins, or otherwise you could impersonate them. But let us know if you think this should behave differently.

@mtanvir21
Copy link
Author

Thanks for the reply, but I think I didn't ask my question clearly, so I apologize for that. So the first admin account I created, let's just call it [email protected]. When I log into the admin portal with this account, I cannot view the admin API token for [email protected]. However, when I log in with accounts that were created after this account, let's call them [email protected] and [email protected], I can view the admin tokens. So if I log in with [email protected] I can view the admin API token for [email protected]. Everything also works with [email protected]. It's just that I cannot view the admin API token for [email protected] while logged in as [email protected]. Does that help out?

@GUI GUI added the bug label Sep 24, 2015
@GUI GUI added this to the v0.9 milestone Sep 24, 2015
@GUI GUI self-assigned this Sep 24, 2015
@GUI
Copy link
Member

GUI commented Sep 24, 2015

Ah, sorry this reply totally slipped past me. This makes sense and is indeed a bug. It should be fixed in master now so that the initial superuser accounts also have this auth token. This will be part of the v0.9 release.

Apologies again for not noticing this sooner and for the super-long delay for a fix!

cc @brylie

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

No branches or pull requests

2 participants