# Triggering a backup via admin API causes the api\_key to become only valid for system user

**URL:** <https://meta.discourse.org/t/triggering-a-backup-via-admin-api-causes-the-api-key-to-become-only-valid-for-system-user/77858>\
**Category:** Bug\
**Created:** [January 12, 2018, 5:00pm UTC](https://meta.discourse.org/t/triggering-a-backup-via-admin-api-causes-the-api-key-to-become-only-valid-for-system-user/77858 "2018-01-12T17:00:56Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [July 10, 2018, 1:45am UTC](https://meta.discourse.org/t/triggering-a-backup-via-admin-api-causes-the-api-key-to-become-only-valid-for-system-user/77858/6 "2018-07-10T01:45:12Z")

</div>

Maybe @zogstrip can have a quick look here, my guess is that something about the restore process may be fussing with api keys post restore.

---

_[View the full topic](https://meta.discourse.org/t/triggering-a-backup-via-admin-api-causes-the-api-key-to-become-only-valid-for-system-user/77858)._
