mirror of
https://github.com/agentrhq/authsome.git
synced 2026-09-19 01:34:19 +08:00
Manoj Bajaj
61515356a2
Align public docs with Principal/Vault/Identity terminology, current daemon API paths, and the CLI/proxy/export integration surface instead of the removed AuthService library API. Co-authored-by: Cursor <cursoragent@cursor.com>
97 lines
2.5 KiB
Plaintext
97 lines
2.5 KiB
Plaintext
---
|
|
title: "Buffer"
|
|
sidebarTitle: "Buffer"
|
|
description: "Store and use your Buffer API key with authsome. Local encrypted vault, proxy injection, no key in the agent's environment."
|
|
icon: "buffer"
|
|
keywords: ["buffer api key authsome", "buffer key broker", "buffer agent credentials", "authsome buffer"]
|
|
---
|
|
|
|
import MultiConnectionsCta from "/snippets/multi-connections-cta.mdx";
|
|
import MaskedInputNote from "/snippets/masked-input-note.mdx";
|
|
import WhatsNextApiKey from "/snippets/whats-next-apikey.mdx";
|
|
|
|
Buffer uses a long-lived API key. Authsome stores the key encrypted in the local vault, injects it at request time through the proxy, and keeps it out of shell history, process listings, and environment dumps.
|
|
|
|
## At a glance
|
|
|
|
| | |
|
|
|---|---|
|
|
| Provider name | `buffer` |
|
|
| Display name | Buffer |
|
|
| Auth type | API key |
|
|
| Header | `Authorization: Bearer <key>` |
|
|
| Proxy host | `api.bufferapp.com` |
|
|
| Env var | `BUFFER_API_KEY` |
|
|
| Where to get a key | [https://publish.buffer.com/developers/apps](https://publish.buffer.com/developers/apps) |
|
|
|
|
## Get a key
|
|
|
|
Create an API key in the Buffer dashboard at [https://publish.buffer.com/developers/apps](https://publish.buffer.com/developers/apps).
|
|
|
|
## Log in
|
|
|
|
```bash
|
|
authsome login buffer
|
|
```
|
|
|
|
A local browser form opens at `http://127.0.0.1:7998`. Paste the key into the masked input and submit.
|
|
|
|
<MaskedInputNote />
|
|
|
|
Verify:
|
|
|
|
```bash
|
|
authsome get buffer --field status
|
|
# → connected
|
|
```
|
|
|
|
## Use the key
|
|
|
|
Run the agent under the proxy (recommended).
|
|
|
|
<CodeGroup>
|
|
|
|
```bash Proxy (recommended)
|
|
authsome run -- python my_agent.py
|
|
```
|
|
|
|
```bash Environment
|
|
eval "$(authsome export buffer --format env)"
|
|
echo $BUFFER_API_KEY
|
|
```
|
|
|
|
</CodeGroup>
|
|
|
|
Under the proxy, authsome sets `BUFFER_API_KEY=authsome-proxy-managed` in the child's environment and injects the real key into outbound requests to `api.bufferapp.com`. The child process never sees the actual value.
|
|
|
|
## Multiple keys
|
|
|
|
<MultiConnectionsCta />
|
|
|
|
```bash
|
|
authsome login buffer --connection personal
|
|
authsome login buffer --connection team
|
|
```
|
|
|
|
## Rotate or remove the key
|
|
|
|
```bash
|
|
authsome login buffer --force # rotate
|
|
authsome logout buffer # remove local credential
|
|
authsome remove buffer # remove all local state for the provider
|
|
```
|
|
|
|
API-key providers have no revocation endpoint, so `revoke` and `remove` are equivalent for Buffer.
|
|
|
|
## Override the bundled definition
|
|
|
|
```bash
|
|
authsome inspect buffer > ~/.authsome/providers/buffer.json
|
|
# edit fields
|
|
authsome list # source now shows "custom" for buffer
|
|
```
|
|
|
|
## What's next
|
|
|
|
<WhatsNextApiKey />
|