# Rake api\_key:get broken

**URL:** https://meta.discourse.org/t/rake-api-key-get-broken/132948
**Category:** Support
**Created:** [8 november 2019 om 17:37 UTC](https://meta.discourse.org/t/rake-api-key-get-broken/132948 "2019-11-08T17:37:38Z")
**Posts on this page:** 1
**Showing post:** 16

<div class="post-metadata">

### Author: ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)
#### Post date: [29 november 2019 om 15:56 UTC](https://meta.discourse.org/t/rake-api-key-get-broken/132948/16 "2019-11-29T15:56:04Z")

</div>

Sorry @pfaffman, but I’m afraid I will have to remove this new rake task in an upcoming PR. We are going to be hashing API keys in the database, so it will be fundamentally impossible to retrieve an existing key.

[https://github.com/discourse/discourse/pull/8438](https://github.com/discourse/discourse/pull/8438)

I’ve replaced the `get_or_create_master` task with a simpler [`create_master` task](https://github.com/discourse/discourse/pull/8438/files#diff-deccd3ec1ab6caa30ce4410492909478L3), which will unconditionally create a new key. If you want to only have one key, then you will need to keep track of the key in your own system.

---

_[View the full topic](https://meta.discourse.org/t/rake-api-key-get-broken/132948)._
