Integration and authentication

<< Click to Display Table of Contents >>

Navigation:  » No topics above this level«

Integration and authentication


Bizagi PaaS is a secure, scalable and reliable subscription-based offer, which provides all of the power of the Bizagi Digital Business platform directly in the cloud.

When modeling your business applications, you can choose to integrate them with your existing services by relying on out-of-the-box Bizagi integration features.




Among these services you may connect with, through the out-of-the-box features, are:

Identity Managers.

Email services.

Document Management Systems or Enterprise Content Managers.

Service-oriented systems offering web services.

Other general applications or cloud services.


Service oriented architectures

Bizagi PaaS introduces a service oriented architecture, which from its very design, has been built for the cloud (i.e, a cloud-centric architecture).

For introductory information about the cloud-centric architecture, refer to Bizagi PaaS architecture.

Within its cloud-centric architecture, Bizagi PaaS leverages connectivity with modern and service-oriented architectures which are cloud-ready as well.



Consider as cloud-ready, systems and services which are either cloud-native, cloud-enabled or simply published for access through a public channel such as internet.

This means basically a service which has an HTTP/HTTPS (the later preferred) endpoint.


To leverage the above, with Bizagi PaaS you may rely on:


SAML 2.0 support, so that you can easily integrate your corporate Identity Manager while enforcing best security practices.

For more information about using integrated authentication in Bizagi so that you can rely on your own Identity Managers, refer to Identity managers.


A generic Web services connector supporting SOAP 1.2 and 1.1, so that you can easily invoke web services using WS-Security standards and without the need of programming (while using graphical configuration to map inputs and outputs).

CMIS 1.0 compliance so that you can use your corporate Document Management System or Enterprise Content Manager, to store attachments within existing document library repositories.

Other features which allow you to plug-in components or connectors targeted to any specific service. Through the features known in Bizagi as Component library or Bizagi Connectors, you may also extend integration capabilities while developing your own code.

For more information about application integration features in Bizagi, refer to Application integration.


Additionally, there are other features aimed at integrating other assets such as: your corporate SMTP e-mail server (to send out notifications or to leverage an Exchange server to allow end users to complete activities via e-mail), existing data sources, or peripheral devices bundled in the Bizagi user interfaces.

For more information about these other features, refer to Integration of other assets.


Bizagi API

On top of the cloud-centric architecture, Bizagi provides programmatic access to the processes functionality and to the business information of your Bizagi data model, by providing a powerful service-oriented API which is ready-for-use for every Bizagi project.

You can rely on this API, whenever there is the need for an external application to do any of the following in Bizagi: fire new process instances, trigger business events or complete process steps, or update business information, among other things.

For this purpose, Bizagi features an OData API as described at Bizagi API.