.png)
Okta OAuth 2.0 Integration
Crassula offers enhanced security and convenience through OAuth 2.0 authentication using Okta Identity. This integration provides users with a unified, seamless, and secure sign-in experience across internal and external applications.
Overview
The Okta OAuth 2.0 integration enables users to access Crassula using their Okta credentials, eliminating the need for separate login details. This streamlined process simplifies user management, increases security, and improves overall user satisfaction.
The main configuration is performed on the Okta side, and Crassula supports the functionality. The integration is enabled in the Crassula system configurations. Please contact your manager for configuration details.
Prerequisites
User profiles must be registered in Okta.
Corresponding user profiles must exist in Crassula.
The Client ID for users in Crassula must match the internal IDs provided by Okta to connect profiles. When profiles are connected, the Okta ID will be shown in the "OktaId" field within the profile's Metadata section.
When a profile is connected to Okta for authentication, manual changes to login and passwords through the admin panel are disabled.
Enabling this feature allows user profiles registered in Okta to be smoothly created in Crassula, enabling a comprehensive single-sign-on (SSO) solution.
Benefits for White Labels
Enhanced Security: OAuth 2.0 with Okta offers a robust authentication method, reducing the risk associated with password management.
Improved User Experience: Users benefit from a seamless login process, increasing overall satisfaction and engagement.
Simplified User Management: Dynamic control of authentication methods allows administrators to quickly adapt and manage user access.
User Experience
Users log in using their Okta credentials through an integrated login widget, enjoying immediate and secure access to the platform. Password changes and registrations are managed directly through Okta, ensuring consistent and secure account management.
Administration
Administrators can dynamically enable or disable OAuth 2.0 authentication via configuration toggles, offering flexibility in managing authentication methods tailored to organizational needs.