# How do people manage ssh forced-commands in authorized public keys?

**URL:** <https://forum.ansible.com/t/how-do-people-manage-ssh-forced-commands-in-authorized-public-keys/13256>\
**Category:** Ansible Project\
**Created:** [August 5, 2013, 4:06am UTC](https://forum.ansible.com/t/how-do-people-manage-ssh-forced-commands-in-authorized-public-keys/13256 "2013-08-05T04:06:03Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Javier\_Candeira](https://avatars.discourse-cdn.com/v4/letter/j/c6cbf5/32.png) [@Javier\_Candeira](https://forum.ansible.com/u/Javier_Candeira)\
**Post date:** [August 5, 2013, 4:06am UTC](https://forum.ansible.com/t/how-do-people-manage-ssh-forced-commands-in-authorized-public-keys/13256/1 "2013-08-05T04:06:03Z")

</div>

Hi,

What's the best practice recommended for managing ssh forced-commands  
in authorized public keys?

I'm thinking of adding a set of command, environment, from options in  
the authorized\_key module, the key can be managed just by the key  
text, but all other options can also be set/unset.

Michael, would you like to have that in core?

J