Multi-Tenancy & Security icon petrol

    Ververica Platform

    Multi-Tenancy & Security

     

    To fit the requirements of enterprise work environments, Ververica Platform is built as a centrally managed solution optimized for multi-tenant architectures. Multi-tenancy support is based on the concept of namespaces: these enable multiple development teams to efficiently work on a shared platform with resource isolation, global best practices and policies, and default configurations that fit your enterprise’s needs.

    Benefits

    Centrally Managed Streaming Platform

    All operational and administrative aspects of Ververica Platform can be defined and managed in a centralized way to increase productivity and compliance. The platform is designed to be shared by all development teams that work with Apache Flink across the organisation.

    Simple, Flexible Access Control

    Ververica Platform provides simple, yet powerful access control for platform resources, ensuring security and isolation in collaborative environments. It controls access to artifacts, Apache Flink components and platform resources in a unified way, facilitating consistent permissions within your system.

     

    Flink Security Best Practices

    Apache Flink has multiple built-in features to ensure authenticated and encrypted communication between cluster components. Ververica Platform extends and adds to these native features with end-to-end security guarantees, from intra-cluster level to user-facing components.

     

    How does it work?

    • Multi-Tenancy & Security
      Multi-Tenancy & Security
    Multitenancy graphic 1000px

    The authentication scheme in Ververica Platform is flexible and able to accommodate the following:

    OpenID Connect (OIDC): Authentication providers implementing the OpenID Connect standard are supported  out-of-the-box. If your organiszation is using a different authentication scheme, such as LDAP (Lightweight Directory Access Protocol) or Active Directory or SAML (Security Assertion Markup Language), integration is also possible.

    API Tokens: To allow programmatic, machine-to-machine access, authentication with API Tokens is supported and bound to authorization configuration for fine-grained access control.


    Authorization is based on roles with associated sets of rules that define the permissions each user (or token) has within a namespace.

    Resources to Get You Started

    Set up a Meeting

    Fill out the form and we’ll have a Ververica expert contact you. Our experts can answer questions, provide more information, and help you understand what our solutions can do for your business.

    By clicking Submit you agree that your personal data submitted via this form will be processed in accordance with the Ververica Privacy Policy.