3. Third-Party Authentication

Third-Party Authentication Overview

Third-party authentication enables users to access Circularo using external identity providers rather than traditional username/password credentials. This approach leverages existing authentication systems to provide a seamless and secure login experience.

What is Third-Party Authentication?

Third-party authentication allows users to:

• Sign in using existing accounts from trusted identity providers

• Access Circularo without creating and managing separate credentials

• Benefit from the security features of established identity platforms

• Experience a streamlined login process with fewer steps

Third-party authentication methods are advanced integration scenarios that typically require coordination with Circularo support team. These methods are not suitable for all integration use cases.

Implementation Considerations

Before implementing third-party authentication:

• Contact Circularo support to whitelist callback URLs and configure provider settings

• Ensure your application can handle the token exchange process

• Be aware that some endpoints are described only in full Circularo OpenAPI schema

When to Use Third-Party Authentication

Third-party authentication is ideal for:

• Enterprise integrations: When your organization already uses identity providers

• Customer-facing applications: To reduce friction in the login process

• Single sign-on environments: Where users expect to access multiple systems with one set of credentials

While third-party authentication provides convenience, standard session tokens or API tokens are recommended for most server-to-server integrations and automated processes.

The third-party authentications may require special permissions or configuration. Contact Circularo support for guidance specific to your integration needs.