Client Enrollment
Enrollment is the secure first-time pairing of a client with the FRP Auto Deploy server. It establishes persistent management identity; it is not the same thing as the published SSH/web connection itself.
Choose the workflow
Zero-Touch
The easiest interactive CLI path is:
Then:
For an explicit SSH profile:
The generated bootstrap command contains a short-lived credential. Send it only through an appropriate private channel.
The SSH user must already exist. FRP Auto Deploy does not create users, enable SSH, change passwords, or install SSH keys.
Manual Enrollment Code
On the server:
The server produces enrollment information including a short-lived Enrollment Code, allocator URL, CA trust/fingerprint material, and a client bootstrap command.
The remote user runs the generated command and enters the Enrollment Code when prompted.
Typical service choices include:
The server owns the public service-port assignment. The client chooses the target host and target port.
Trust establishment
After that, normal supported operations use the persistent identity rather than repeatedly using the first-install secret.
Verify enrollment
Server:
Client:
Stable v2.1.2 enrollment lifecycle
Use the non-secret enrollment ID to revoke an active credential:
show enrollments never prints the secret itself.
The 2.1.3 development tree adds more explicit terminal enrollment-retention/purge operations. Those are development-channel behavior and are not documented here as stable v2.1.2 commands.
Persistent identity
A successful enrollment creates a persistent CLIENT ID and management identity. Normal service edits, reboots, and supported updates do not require re-enrollment.