Integrations

/

Akamai Identity Cloud SAML2 SSO with Flexopus

Manage access to Flexopus centrally via Akamai Identity Cloud – secure, simple, and without manual user maintenance.

No items found.
No items found.

What is the Akamai Identity Cloud SAML2 SSO integration?

The Akamai Identity Cloud SAML2 SSO integration connects Flexopus with Akamai using the SAML2 (Security Assertion Markup Language) protocol. Akamai acts as the Identity Provider (IdP): users authenticate with their existing corporate credentials in Akamai and are automatically granted access to Flexopus – without needing a separate password.

Upon the first successful login, the user profile is automatically created in Flexopus. In addition to the basic login, optional attributes such as department or job title can be transferred from Akamai to Flexopus.

What is the purpose of the integration?

The integration ensures that employees can log in to Flexopus using a single set of credentials – their familiar corporate data. This saves time, reduces password-related issues, and increases security.

Typical use cases include:

  • Centralized access management: Administrators define in Akamai which users or groups have access to Flexopus. Changes take effect immediately.
  • Automatic user provisioning: New employees are automatically registered in Flexopus upon their first SSO login – with no manual effort for administrators.
  • No separate password: Employees use their existing Akamai credentials and do not need to remember an additional password.

How easy is the setup?

Setting up the Akamai SAML2 SSO integration takes just a few steps. Essentially, a new SAML2 application for Flexopus is created in Akamai, the necessary parameters (Entity ID, ACS URL) are taken from the Flexopus settings, and the metadata file from Akamai is then uploaded into Flexopus.

A complete step-by-step guide for setup can be found in our Help Center.

What are the benefits of the integration?

  • Single Sign-On: Employees log in with their existing corporate credentials – no additional password required.
  • Automatic user registration: New users are automatically created in Flexopus upon their first login, with no manual data maintenance.
  • Centralized access management: Access is controlled directly in Akamai – including group and user management.
  • Higher security: The SAML2 protocol ensures secure authentication. Optional deactivation of email/password login is possible.
  • Minimal data exchange: Only necessary user attributes are transferred (name, email, UPN). Optional fields like department or job title can be synchronized additionally.
  • Included for free: The integration is included in the Flexopus subscription (depending on the chosen plan) – at no extra cost.
Categories
Developed By
Flexopus GmbH
Frequently Asked Questions

Questions and answers

Are user profiles created automatically?

Yes. After the first successful SAML2 SSO login, the user profile is automatically created in Flexopus. Manual pre-creation is not required. This default setting is recommended and should only be disabled in exceptional cases.

What happens if a user is deleted or deactivated in Akamai?

If a user is deactivated or removed from the application in Akamai, they can no longer log in to Flexopus. However, the user profile remains in Flexopus and must be deactivated or deleted there separately if necessary.

Can I change a user's UPN (Unique Principal Name) later?

The UPN is a unique identifier and should not be changed. A change can lead to a duplicate user profile being created in Flexopus. If a change is absolutely necessary, please contact Flexopus support at support@flexopus.com.

Are profile pictures synchronized from Akamai?

No. The SAML2 protocol does not support the transfer of profile pictures. Profile pictures must be uploaded directly in Flexopus.

Does Flexopus support IdP-initiated login?

Yes, with a workaround. By configuring the "initiate-sp-login" parameter for the RelayState, the IdP-initiated login is converted into a secure SP-initiated login. This prevents potential security vulnerabilities (e.g., man-in-the-middle attacks) while still allowing direct login from the Akamai dashboard.