Hello. <http://portal.airbyte.com/> having DNS Pro...
# help-api-cli-orchestration
s
Hello. http://portal.airbyte.com/ having DNS Problems. Is there another way of managing API credentials? @Bryce Groff (Airbyte)?
u
Yes, there are several ways to manage API credentials in Airbyte. For Airbyte Open Source, credentials like API Keys and passwords are stored in the Airbyte application database. You can protect these credentials by securing the [configuration management routes](https://airbyte-public-api-docs.s3.us-east-2.amazonaws.com/rapidoc-api-docs.html). If you're deploying Airbyte Open Source on GCP, you can use Google [Secret Manager](https://cloud.google.com/secret-manager) to store credentials instead of in the database. This involves creating a service account with Google Secret Manager, setting environment variables in the Worker and Server applications, and changing the
SECRET_PERSISTENCE
environment variable to
GOOGLE_SECRET_MANAGER
[source](https://docs.airbyte.com/operator-guides/security). For Airbyte Cloud, credentials are fetched using HTTPS and stored in Google Cloud’s [Secret Manager](https://cloud.google.com/secret-manager). When persisting connector configurations to disk or the database, a version of the configuration that points to the secret in Google Secret Manager is stored instead of the secret itself [source](https://docs.airbyte.com/operator-guides/security). You can also use the [secret management feature](https://docs.airbyte.com/cli-documentation#secret-management) in the Airbyte CLI to avoid storing credentials in the YAML files [source](https://docs.airbyte.com/cli-documentation). Please note that Airbyte currently uses basic authentication and does not support API keys [source](https://airbytehq.slack.com/archives/C021JANJ6TY/p1677068339102509). You can change the default username and password in your environment's
.env
file [source](https://docs.airbyte.com/operator-guides/security). For specific connectors, you may need to follow their respective documentation to get the API credentials. For example, for the Customer.io connector, you can follow [their documentation for generating an App API Key](https://customer.io/docs/managing-credentials/) [source](https://docs.airbyte.com/integrations/sources/customer-io).
b
Looks like this is no longer an issue. Can you try again