Authentication Objects

Authentication Objects provide a secure, centralised way to store and manage the credentials used by API integrations.

Instead of storing usernames, passwords, API keys or OAuth credentials within individual API calls, you create an Authentication Object once and reference it wherever it is needed. This simplifies administration, improves security, and makes credential updates much easier.

Use the guides below to learn how to create, manage and use Authentication Objects.

Getting started

Create an Authentication Object

Learn how to configure Authentication Objects for supported providers, validate the connection, and securely store credentials.

• What is an Authentication Object and how do I configure it?

View Authentication Objects

Learn about the Authentication Objects list, available columns, actions, and how to monitor Authentication Objects across your system.

• Authentication Objects List

Using Authentication Objects

Configure API calls

Learn how to reference an Authentication Object from an API Call actor so that integrations can authenticate securely.

• Using an Authentication Object in an API Call

Managing Authentication Objects

Update credentials

Learn what happens when you edit an Authentication Object, how updates affect existing integrations, and what to expect when changing credentials.

• What happens if I edit an Authentication Object?

Things to remember

1. Authentication Objects allow credentials to be stored securely in one central location.
2. A single Authentication Object can be reused by multiple API Call actors.
3. Updating an Authentication Object automatically updates every integration that references it.
4. Authentication Objects support a range of built-in providers, including OAuth, API Key, DocuSign and Autologyx Internal authentication.

Autologyx Classification: Unrestricted, Public