Target audience: Workspace administrators and developers running service account integrations
Overview
This article covers how to connect (mount) the LucidLink daemon to a filespace using a service account's secret key, without a user login. It applies to both collaborator and admin service accounts. To replace a secret key while the daemon stays linked, see Manage service account keys.
Mount a filespace with a service account
You'll need a secret key for the service account. If you don't have one, create it on the service account's Secret keys tab. See Manage service account keys.
1. Start a daemon and connect to a filespace:
lucid [--instance N] daemon --fs filespace.name --login-token [token]2. Or connect a daemon that is already running:
lucid [--instance N] link --fs filespace.name --login-token [token]In both commands, --instance N is optional. Use it when you run more than one daemon on the same machine. If you leave out the token, you're prompted to enter it securely.
For all options, run lucid help, lucid help daemon, or lucid help link.
Frequently Asked Questions
Can a service account connect when my workspace requires SSO or two-factor authentication?
Yes. Service accounts can connect to a filespace through the command line, even in workspaces with required SSO or enforced 2FA.
What can the daemon access when it's linked with a collaborator service account?
Only the filespaces and folders granted to that collaborator service account, with the read or write permission you set. See Collaborator Service Accounts (GA).
Are actions taken through the daemon recorded in the audit log?
Yes. File actions appear in the filespace audit log under the service account's name.
Do I have to put the secret key in the command?
No. If you leave out the token, the CLI prompts you to enter it. Use the prompt to keep the secret key out of your shell history and process lists.