# Adicionando suporte a ferramentas de linha de comando para chaves de API do usuário

**URL:** <https://meta.discourse.org/t/adding-command-line-tools-support-for-user-api-keys/103803>\
**Category:** Development\
**Created:** [6 Dezembro , 2018 23:21 UTC](https://meta.discourse.org/t/adding-command-line-tools-support-for-user-api-keys/103803 "2018-12-06T23:21:13Z")\
**Posts on this page:** 1\
**Showing post:** 16

<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:** [11 Dezembro , 2018 02:12 UTC](https://meta.discourse.org/t/adding-command-line-tools-support-for-user-api-keys/103803/16 "2018-12-11T02:12:26Z")

</div>

> [@cfitz](#):
>
> Sounds like there’s a complication with the requirement for an RSA key pair.

Keep in mind nothing is bundled, you hand the server your public key, it then encrypts your token using it. I know it may feel a bit overkill but I do not want to amend the protocol here. So when you “show” the api key to the user actually show the **encrypted** api key. Your CLI can then decrypt it cause it holds the private key.

---

_[View the full topic](https://meta.discourse.org/t/adding-command-line-tools-support-for-user-api-keys/103803)._
