NO TITLE FOUND
- Last Updated: November 19, 2026
- 3 minute read
- Documentation
Progress Data Platform verifies the identity of every user and application that connects to it. This topic describes how people, applications, and AI agent clients authenticate to Data Platform. For information about how roles control what each identity can do, see Share access.
This topic covers the following:
- How authentication works
- User authentication
- API key authentication
- Authentication for AI agent clients
- Security recommendations
How authentication works
Data Platform authenticates every request before it processes the request. Data Platform then checks whether the authenticated identity has permission to perform the requested action on the requested data. Requests that are not authenticated, or that use credentials for one account to access another account, are rejected.
Data Platform supports the following types of identities:
| Identity | Used by | How it authenticates |
|---|---|---|
| User | People who work in Data Platform through a browser. | Sign-in with an email address and password, or with single sign-on (SSO). |
| API key | Applications, scripts, and automated workflows that use the Data Platform API or command-line interface. | An API key created in Progress account management. |
| AI agent client | External AI agents and assistants that connect to project data through the Model Context Protocol (MCP). | Interactive sign-in through OAuth, or an API key. |
User authentication
Users sign in to Data Platform through Progress account management. An account owner chooses how to sign in when activating the account, and team members sign in after they accept an invitation. Users can sign in with an email address and password, or with SSO through their organization's identity provider.
A user must belong to an account to use Data Platform. Joining an account does not grant access to its projects. Project access is granted separately for each project. See Share access for more information.
When a user switches accounts, Data Platform uses the roles that the user has in the selected account. The same person can have different roles in different accounts.
For more information, see the following topics:
API key authentication
API keys let applications and automated workflows authenticate to Data Platform without a user's credentials. In some parts of the user interface, such as the user menu, API keys are called NUA keys.
API keys have the following characteristics:
Keys belong to an account.
A key can access only the account that it was created for.
Keys have no project access by default.
You must grant a key access to each project that it needs to work with.
Key secrets are shown only once.
For security reasons, account management displays a key's secret only once, in a pop-up window when you create the key. You cannot view the secret again later, so copy it and store it securely before you close the window.
For instructions on creating keys, managing their platform roles, and granting project access, see Manage API keys. For information about using keys with the API, see Progress Data Platform API.
Authentication for AI agent clients
Data Platform provides a Model Context Protocol (MCP) endpoint for each project, which external AI agents and assistants can use to work with project data. MCP clients can authenticate in the following ways:
- OAuth: For interactive clients, such as AI assistants on a desktop. The client discovers the Data Platform authorization server and prompts you to sign in through your browser. The client then acts with your identity and your project access.
- API key: For automated clients. Send an API key that has access to the account and to the project. access is sufficient to read project data.
An MCP client can use only the tools that its identity has permission to use.
For instructions, see Connect MCP clients to Data Platform.
Security recommendations
Follow these recommendations to keep your credentials secure:
Use API keys for automation.
Do not share user credentials with scripts or applications.
Protect API key secrets.
Store key secrets in a secrets manager, and do not commit them to source control.
Grant API keys only the access they need.