Microgateway 10.5 | webMethods Microgateway Help | Policies | Identify and Access | Identify and Authorize Application | Application Synchronization to support Identity and Access Management Policy
 
Application Synchronization to support Identity and Access Management Policy
For Microgateway to support the Identity and Access Management (IAM) policies it is necessary that Microgateway has the recently updated applications from the API Gateway instance from where the applications are provisioned. Microgateway provides a mechanism to synchronize applications between API Gateway and Microgateway to support the IAM policy.
During API provisioning the applications are pulled from the API Gateway instance into Microgateway. After provisioning these applications in Microgateway, these applications have to be in synchronization with those in API Gateway, from where they are provisioned, so that any changes in the applications in the API Gateway instance is reflected in the Microgateway. This helps the IAM policy execution for an API in Microgateway validate with the latest applications instead of validating against the stale application data.
Application synchronization in Microgateway is achieved through a polling mechanism. To avoid the consumption of a considerable amount of memory and CPU, the API Provider provides certain configurations for polling the applications to minimize the memory and CPU utilization. Polling can be done for the following parameters:
*List of application ids
*All registered applications of the APIs in Microgateway
*All global applications
The property applicationstoSync is configured for polling the applications where you can specify the parameters in the format registeredapplication, all, or comma separated ids.
Considerations during application synchronization:
*Microgateway is provisioned with the application synchronization configuration before start up.
*Only one thread runs for synchronization.
*When the thread execution crashes, it starts again.
*A timestamp of the last synchronized application is maintained in the Microgateway instance so that the next polling would be for applications updated > timestamp.
*A property to specify the polling interval is added.
*A property to enable or disable synchronization is added.