Skip to content
Fluxer API

Bluesky account linking

People can link a Bluesky account to their profile. Bluesky has no developer registration and hands out no API keys. Your instance makes its own signing key, and Fluxer publishes the public half for Bluesky to check.

The key has to be an ES256 key on the P-256 curve, which Bluesky requires. You can make one with OpenSSL.

Terminal window
openssl genpkey -algorithm EC -pkeyopt ec_paramgen_curve:P-256 -out bluesky-key.pem

Keep the file secret. Anyone with it can sign requests as your instance.

Each key has a key ID, which is any name you pick, such as key-1. Use one of these.

  • Admin panel. Open Instance Config, go to Runtime Integrations and find Bluesky OAuth. Enter the key ID under New signing key ID and paste the whole PEM file, including the BEGIN and END lines, under New private key. Saving there replaces every key Fluxer had before.
  • Environment. Set FLUXER_AUTH_BLUESKY_KEYS to a JSON array. Each entry has a kid and either a private_key with the PEM text or a private_key_path with an absolute path inside the api and worker containers. For example, [{"kid":"key-1","private_key_path":"/etc/fluxer/bluesky-key.pem"}]. With rexctl, use rexctl config set integrations.bluesky.keys.

Keys saved in the admin panel replace the ones from the environment.

Set Bluesky OAuth to enabled in the admin panel, or set FLUXER_AUTH_BLUESKY_ENABLED to true. With rexctl, use rexctl config set integrations.bluesky.enabled true. The name, logo, terms and privacy links Bluesky shows are optional and listed under Integrations.

Bluesky fetches two documents from your instance while someone links an account, so FLUXER_API_ENDPOINT has to work over public HTTPS. Open both in a browser.

  • <FLUXER_API_ENDPOINT>/connections/bluesky/client-metadata.json
  • <FLUXER_API_ENDPOINT>/connections/bluesky/jwks.json

The second one lists the public half of each key under its key ID. When both load, people can link an account from their profile settings.

To move to a new key, add it next to the old one in FLUXER_AUTH_BLUESKY_KEYS with its own key ID, restart, and remove the old one later. The admin panel holds one key at a time, so saving a new one there switches straight away.