API generally stands for Application Program Interface. It creates a bridge / medium for two different software programs / units.
Let’s say that the business leaders are planning for increasing the efficiency and proficiency of their business in terms of growth.
So they would create the set of processes or software programs (Server) which then it provides the service to their clients (Client) with the help of API.
Producer:- An Entity who produces the API’s to serve their clients.
Consumer:- An Entity who consumes the produced API’s from their Service Provider.
It takes more time and cost while Integrating third-party API’s in Traditional Application.
For Instance, Implementing SSO Single Sign-On Mechanism in traditional app development ( Angular / React as a client-side scripting with NodeJS / Java / Ruby as a server-side scripting ).
In general, to implement SSO, we need to create an application in IdP – Identity Protocol ( Like Okta, Lastpass, OpenIDConnect, Keycloak ).
To implement SSO in the traditional application, it would hardly take 6 – 8 hours, since we need to configure those IdP credentials in SP’s – Serivice Provider’s with the help of SAML Module.
SAML stands for Security Assertion Markup Language is an open standard for exchanging authentication and authorization data between parties, in particular, between an identity provider and a service provider.
Whereas in mendix, implementing an SSO Mechanism is a low-code platform, so by integrating MxModelReflection, SAML Mendix App Store modules and Mendix defaults actions and java actions.
By making use of SAML Module we would be easily able to configure the IdP details.
Let’s see the sample Mendix – SSO Application creation with the help of OKTA Third party API.
(Note: Mx model reflection is necessary for SAML to operate)
FirstName and select user.firstName from drop down.
LastName and select user.lastName from drop down.
Email and select user.email from drop down.
That’s it. Here we go, save and run the application.
and check the url : https://localhost:8080/sso/
It just takes hardly 45 minutes to 1 hour, and it saves around 5 – 7 hours approximately when comparing to traditional app development. That’s the beauty and impact of Mendix.
To handle integrations, Mendix offers a wide array of tools:
Message definition – Specify the messages that are being exchanged with external systems.
Mappings – Leverage visual specifications on how to translate external messages from and to entities in Mendix applications.
Web services – Microflows should be published as web service operations, with external web services called from microflows.
REST services – Microflows and entities should be published as REST resources and operations, with external REST APIs called from microflows.
Database integration – Database connector in Mendix enables to configure direct JDBC connections to your chosen database to execute stored procedures and SQL queries.
This blog post covers implementing 3rd Party API’s Mendix Integration. This offer’s a number of unique advantages over more traditional development.
Furthermore, we have demonstrated that Mendix application deployments could be much simpler than ever expected
By Uma Raj
By Uma Raj
By Abishek Balakumar