If you cannot remember the email used for Airbyte authentication, you can retrieve it by running:

abctl local credentials

This command will display the current authentication email along with the password and other credentials. If you want to change the authentication email, you can do so with:

abctl local credentials --email YOUR_NEW_EMAIL

After setting a new email, you can use it (along with the password shown by the credentials command) to log in to Airbyte. If you need to set a new password as well, you can use the

--password

flag in the same command [FAQ - Unable To Locate User Email](https://docs.airbyte.com/platform/next/deploying-airbyte/troubleshoot-deploy#faq) [abctl reference](https://docs.airbyte.com/platform/next/deploying-airbyte/abctl#reference).

If you are not using abctl and are only accessing Airbyte through the UI, the knowledge sources do not provide a direct method to retrieve or change the authentication email from within the Airbyte UI itself. All documented methods for viewing or updating the authentication email require the use of abctl or direct interaction with Kubernetes secrets, not the UI. If you deployed Airbyte using Kubernetes and Helm, you may be able to retrieve the credentials (including the email) from the Kubernetes secret named

airbyte-auth-secrets

in your namespace. However, the knowledge sources do not specify that the email is stored in this secret—only the password, client-id, and client-secret are mentioned as being retrievable this way. In summary, if you do not have access to abctl or the Kubernetes cluster, the knowledge sources do not describe a way to view or change the authentication email from the Airbyte UI alone. If you have access to the underlying infrastructure, you may be able to reset or update credentials using abctl or by modifying Kubernetes secrets, but this is not possible solely through the UI according to the available documentation [Authentication](https://docs.airbyte.com/platform/next/deploying-airbyte/integrations/authentication).

If you set up Airbyte using kubectl and Helm templates (not abctl), the knowledge sources indicate that the authentication credentials (password, client-id, client-secret) are stored in the Kubernetes secret named

airbyte-auth-secrets

in your Airbyte namespace. However, the documentation does not mention that the email is stored in this secret—only the password and API credentials are included. You can retrieve the secret with:

sh kubectl get secret airbyte-auth-secrets -n <YOUR_NAMESPACE> -o yaml

The output will contain base64-encoded values for

instance-admin-password

,

instance-admin-client-id

, and

instance-admin-client-secret

. You can decode them using:

sh echo '<base64-value>' | base64 -d

Regarding the email: The knowledge sources do not specify where the authentication email is stored or how to retrieve or change it when deploying with Helm and kubectl. The email is typically set during the initial setup, but if you did not explicitly set it or do not remember it, there is no documented way to retrieve or reset it via Kubernetes secrets or the UI. Summary: - You can retrieve the password and API credentials from the Kubernetes secret. - The email is not included in the secret, and the documentation does not provide a method to view or change it when using Helm/kubectl. - If you are locked out due to a forgotten email, the knowledge sources do not provide a solution for this scenario. For more details, see the [Authentication documentation](https://docs.airbyte.com/platform/next/deploying-airbyte/integrations/authentication).

You are correct—according to the documentation at [Authentication](https://docs.airbyte.com/platform/next/deploying-airbyte/integrations/authentication), there is no mention of how the authentication email is set, stored, or retrieved when deploying Airbyte with Helm and kubectl. The documentation only describes how to set or retrieve the password and API credentials via the

airbyte-auth-secrets

Kubernetes secret, but does not reference the email at all. Therefore, based on the available knowledge sources, there is no documented way to view, retrieve, or reset the authentication email when using Helm and kubectl. If you do not remember the email you used, the documentation does not provide guidance for this scenario.