# Specific identity is not available

**URL:** <https://hub.mender.io/t/specific-identity-is-not-available/418>\
**Category:** General Discussions\
**Tags:** api\
**Created:** [March 26, 2019, 8:45am UTC](https://hub.mender.io/t/specific-identity-is-not-available/418 "2019-03-26T08:45:31Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![moqmar](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/moqmar/32/445_2.png) [@moqmar](https://hub.mender.io/u/moqmar)\
**Post date:** [February 11, 2020, 7:57am UTC](https://hub.mender.io/t/specific-identity-is-not-available/418/7 "2020-02-11T07:57:39Z")

</div>

Yes, this works for the Inventory API, but I can’t use the Device’s _identity_ here, only the metadata of the device, which can change at any time. It would be enough if that format would be supported by the Device Authentication API (`/api/management/v2/devauth/devices?mac=12:34:...` instead of `/api/management/v1/inventory/devices?mac_eth0=12:34:...`), but it isn’t - the mac address obviously is a bad example as it exists both in the metadata and in the identity, but if I change the script in `/usr/share/mender/identity/mender-device-identity`, those values will be fully independent from each other.

---

_[View the full topic](https://hub.mender.io/t/specific-identity-is-not-available/418)._