Security

10 documents tagged with "Security"

Actions on Workspace

Rename a NocoDB workspace, require two-factor authentication, delete or leave a workspace, and find the workspace ID.

Sign Out of Other Devices ☁

End every other NocoDB session on your account from Account Settings, and optionally disconnect the AI apps that you connected.

Two-Factor Authentication ☁

Turn on and manage two-factor authentication (2FA) for your NocoDB account.

Updating Secrets

Update secrets in NocoDB with the nc-secret-mgr package, from the CLI or an executable.

Connect AWS Secrets Manager

Connect AWS Secrets Manager to NocoDB as an Enterprise vault: create an IAM policy, an IAM user and an access key, then reference secrets from your integrations.

Connect Azure Key Vault

Connect Azure Key Vault to NocoDB as an Enterprise vault: register an Entra ID application, give it read access to the Key Vault, then reference secrets from your integrations.

Connect CyberArk Conjur

Connect CyberArk Conjur to NocoDB as an Enterprise vault: load a policy with a host and variables, then reference the variables from your integrations with the host API key.

Connect Google Secret Manager

Connect Google Secret Manager to NocoDB as an Enterprise vault: create a service account with secret access, add its key, then reference secrets from your integrations.

Connect HashiCorp Vault

Connect HashiCorp Vault to NocoDB as an Enterprise vault: write a policy, create an AppRole, then read secrets from a KV v2 mount in your integrations.

Enterprise Vaults

NocoDB Enterprise Vaults read integration credentials from your own secrets manager (HashiCorp Vault, AWS Secrets Manager, Azure Key Vault, Google Secret Manager or CyberArk Conjur), so NocoDB stores a reference instead of the secret.