# authorized\_key key path broken?

**URL:** <https://forum.ansible.com/t/authorized-key-key-path-broken/14229>\
**Category:** Ansible Project\
**Created:** [December 27, 2013, 9:54pm UTC](https://forum.ansible.com/t/authorized-key-key-path-broken/14229 "2013-12-27T21:54:00Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![t2d](https://avatars.discourse-cdn.com/v4/letter/t/5daacb/32.png) [@t2d](https://forum.ansible.com/u/t2d)\
**Post date:** [December 27, 2013, 9:54pm UTC](https://forum.ansible.com/t/authorized-key-key-path-broken/14229/1 "2013-12-27T21:54:00Z")

</div>

Today, we updated from ansible 1.3 to 1.4.3

This part of the play worked until now

```auto
- name: ensure key files for ssh are present
action: authorized_key
user={{ item }}
key='files/{{ item }}.pub'
with_items:
- user1
- user2

```

but now, we get those errors

```auto
TASK: [common | ensure key files for ssh are present] *************************
failed: [example.org] => (item=user1) => {"failed": true, "item": "user1"}
msg: invalid key specified: files/user1.pub
failed: [example.org] => (item=user2) => {"failed": true, "item": "user2"}
msg: invalid key specified: files/user2.pub

```

The files are still in the same place. Does this happen on purpose and what is the right way to do this now?

---

<div class="post-metadata">

**Author:** ![Michael\_DeHaan2](https://avatars.discourse-cdn.com/v4/letter/m/da6949/32.png) [@Michael\_DeHaan2](https://forum.ansible.com/u/Michael_DeHaan2)\
**Post date:** [December 29, 2013, 2:31pm UTC](https://forum.ansible.com/t/authorized-key-key-path-broken/14229/2 "2013-12-29T14:31:28Z")

</div>

This email looks remarkably similar to a bug report where I asked if you could share your authorized\_key file (ideally sanitized) so we could take a look.

If this was yours please comment on the bug ticket.