jf config export

Create a Config Token from a server configuration. Use the token with jf config import on another machine.

Synopsis

jf config export [server-id]

Aliases: jf c ex

Arguments

ArgumentRequiredDescription
server-idNoExport only this server. Omit to export the active server

Examples

Export a Server Configuration

jf config export <server-id>

When to Use

Use jf config export when you need to transfer a server configuration to another machine — for example, setting up a colleague's development environment or configuring a new CI/CD agent.

Typical workflow:

# On machine A: export the config
TOKEN=$(jf config export my-server)
echo "$TOKEN"  # Copy this token securely

# On machine B: import the config
jf config import <paste-token-here>

Important Notes

  • Security: The exported Config Token contains credentials. Never log it, print it in CI output, or store it in version control.
  • Omit server ID: When you omit the server ID, the currently active server is exported.
  • Token lifetime: The Config Token itself does not expire, but the credentials inside it (access tokens, passwords) have their own expiry.

What’s Next

To apply this token on another machine, see jf config import.