# \[Feature request\] Signed configure

**URL:** <https://hub.mender.io/t/feature-request-signed-configure/5117>\
**Category:** General Discussions\
**Tags:** feature-request\
**Created:** [July 14, 2022, 12:33pm UTC](https://hub.mender.io/t/feature-request-signed-configure/5117 "2022-07-14T12:33:30Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Aalex](https://avatars.discourse-cdn.com/v4/letter/a/eb9ed0/32.png) [@Aalex](https://hub.mender.io/u/Aalex)\
**Post date:** [July 14, 2022, 12:33pm UTC](https://hub.mender.io/t/feature-request-signed-configure/5117/1 "2022-07-14T12:33:30Z")

</div>

I do understand that the configure service uses the deployment mechanism to apply the configuration and therefore can not work when signed artifacts are activated.

A nice way to overcome this problem would be a field where one can drop a signed json config that gets then sent to the server.

---

<div class="post-metadata">

**Author:** ![kacf](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/kacf/32/146_2.png) [@kacf](https://hub.mender.io/u/kacf)\
**Post date:** [July 15, 2022, 9:18am UTC](https://hub.mender.io/t/feature-request-signed-configure/5117/2 "2022-07-15T09:18:01Z")

</div>

It can work if you make and sign the artifact yourself. IIRC the build line goes something like this:

```bash
mender-artifact write module-image \
    -T mender-configure \
    -t raspberrypi4 \
    -n my-artifact \
    -k <SIGNING_KEY> \
    -m <JSON_CONFIG_FILE>

```

Not quite as convenient as what your proposed, but possible.