USERS

This view contains information about users for a given workspace.

If you (the current user) has the GRANT permission, you can see all role-group pairs in this view. Otherwise, you will see only the pairs from groups you are part of.

Column Name	Description
`USER`	The name of a given user.
`HOST`	The hostname or IP address for a given user.
`TYPE`	The type of connection authentication.
`CONNECTIONS`	The number of connections a given user has open.
`IS_DELETED`	Whether a given user had been deleted.
`LAST_UPDATED`	The timestamp at which a given user was last updated.
`DEFAULT_RESOURCE_POOL`	The default resource pool for a given user.
`IS_LOCAL`	Whether a given user is local to the node on which USERS table is being accessed or if it’s a distributed user.
`CREATED`	The timestamp at which a given user was created.
`PASSWORD_EXPIRATION`	If the `password_expiration_seconds` engine variable is not enabled, this column will be NULL. If the `password_expiration_seconds` engine variable is enabled, the column will display the number of seconds remaining for the password to expire.
`PASSWORD_UPDATED`	The timestamp a given user’s password was last updated.
`EFFECTIVE_FAILED_LOGIN_ATTEMPTS`	The number of failed login attempts for a given user.
`EFFECTIVE_PASSWORD_LOCK_TIME`	The amount of time, in milliseconds, a given user’s account has been locked due to failed login attempts.
`ACCOUNT_STATUS`	Whether a given user account is `LOCKED` due to failed login attempts exceeding the set limit, or if the account is `OPEN`. `N/A` means that a policy has not been set for exceeding login attempts.
`ATTRIBUTE`	An optional user field. A JSON object set by including `ATTRIBUTE` as part of ``CREATE USER` or `ALTER USER`.
`COMMENT`	An optional user comment text string for the user. A comment is set by including `COMMENT` as part of `CREATE USER` or `ALTER USER`.

Last modified: April 12, 2023

Was this article helpful?

Verification instructions

Note: You must install cosign to verify the authenticity of the SingleStore file.

Use the following steps to verify the authenticity of singlestoredb-server, singlestoredb-toolbox, singlestoredb-studio, and singlestore-client SingleStore files that have been downloaded.

You may perform the following steps on any computer that can run cosign, such as the main deployment host of the cluster.

(Optional) Run the following command to view the associated signature files.
Shell
```
curl undefined
```
Download the signature file from the SingleStore release server.
- Option 1: Click the Download Signature button next to the SingleStore file.
- Option 2: Copy and paste the following URL into the address bar of your browser and save the signature file.
- Option 3: Run the following command to download the signature file.
  Shell
```
curl -O undefined
```

After the signature file has been downloaded, run the following command to verify the authenticity of the SingleStore file.

Shell

echo -n undefined |
    cosign verify-blob --certificate-oidc-issuer https://oidc.eks.us-east-1.amazonaws.com/id/CCDCDBA1379A5596AB5B2E46DCA385BC \
      --certificate-identity https://kubernetes.io/namespaces/freya-production/serviceaccounts/job-worker \
      --bundle undefined \
      --new-bundle-format -

Verified OK