MLflow tokens · Container tokens
Issue, revoke and audit MLflow tracking tokens and container registry (docker login) tokens
Required permission: SettingsADMIN
Programs outside the platform use tokens instead of passwords to access this tenant. A token is bound to the tenant it was issued in, so it reaches only that tenant. There are two kinds.
| Kind | Used for | Who can issue |
|---|---|---|
| MLflow token | The MLflow client in training scripts and notebooks (MLFLOW_TRACKING_TOKEN) | DEVELOPER · OPERATOR · ADMIN |
| Container token | The password for docker login — push/pull to the built-in registry | Every member (push needs the develop permission — only DEVELOPER, OPERATOR and ADMIN pass) |
Developers usually reach these two screens through Manage MLflow tokens (MLflow 토큰 관리) and Manage container tokens (컨테이너 토큰 관리) in Account settings (계정 설정) in the avatar menu. The screens are the same, but the list scope depends on the role. An ADMIN sees every token in the tenant and audits and revokes them; other roles see only their own tokens. Tokens issued by someone else carry " · Issuer ( · 발급자 <이메일>)".
MLflow tokens
-
Enter a token name (what it is for; optional) and the number of days until expiry (default 90), then press Issue (발급). Leave No expiry (무기한) off unless the token must last a long time.
-
Right after issuing, a card at the top of the screen shows the secret and two lines to copy as they are, only once. The tracking address of this server is already filled in.
export MLFLOW_TRACKING_URI=<tracking URI> export MLFLOW_TRACKING_TOKEN=<issued token> -
Once you leave this screen you cannot see the secret again (the server does not keep the original). If you lose it, revoke it and issue a new one.
Container tokens
The issuing flow is the same, and the issue card shows a complete docker login command to copy.
docker login <registry host> -u <tenant code in lower case> -p <issued token>Any user name works (the token is the password). If the registry is an HTTP address other than localhost, you must add the host to insecure-registries in the Docker daemon configuration before you can log in.
Revoking and auditing
- Press Revoke (회수) on a row and confirm, and the token becomes unusable immediately. The issuer or a tenant ADMIN can revoke it. For someone else's token, the confirmation dialog shows the issuer.
- Tokens with 14 days or less left get an "Expires within N days (N일 내 만료)" badge. Hide revoked and expired (회수·만료 숨기기) shows only live tokens.
- Issuing and revoking are recorded in the audit log as
mlflow_token.*andregistry_token.*.