Navigation: » No topics above this level«
Environments identity and access management
Bizagi can be integrated with a variety of systems that are intended for different purposes. Usually, when a system is integrated with another, an authentication procedure must be executed first, to make sure that the integration occurs only between trusted systems. Due to the variety of systems, and their inherent technologies, access to these systems demand to handle a set of different authentication protocols, for each feature in Bizagi that can be integrated with other systems.
The following picture shows an example where you can have multiple integrations throughout different features available in Bizagi:
Each feature can use a different authentication protocol. Therefore it is important to understand the protocols available for each feature. The following table sums the different integration types, their available authentication protocols. Click on each item to see the authentication protocols.
|HTTP basic authentication||Sharepoint On-premises, Documentum, Alfresco, FileNet|
|OAuth 2.0||Client Credentials, Bearer token|
|Basic HTTP authentication||N/A|
|WS-Security||Basic user profile|
Additional to authentication protocols set for integrations and features, there are other aspects of security that you can configure. You may define the following security aspects in a project:
Work Portal Security
Bizagi allows you to restrict access to different areas of your processes during execution to make sure that the correct people have the necessary privileges and prevent unauthorized actions.
Bizagi offers the Security Module that allows you to define a schema of permissions on some of the elements, which includes:
•How are users authenticated.
•What options can each user see or use (according to roles, positions, location, etc).
•Which processes and tasks are available for mobile device access.
For more information refer to Work Portal Security.