Liferay DXP Features

 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. SAML is an XML-based markup language for security assertions. Wikipedia


Identity Management and Access Control (Application Security)

SAML / Opensso / LDAP / OAuth /User Management (creation , Manage,) Roles , Organisation , permission



Comments

Post a Comment

Popular posts from this blog

Azure App Service for Liferay DXP Installations

 Azure App Service is generally not the optimal choice for hosting Liferay DXP (Digital Experience Platform) installations. Liferay DXP is a robust, enterprise-grade platform that requires specific configurations and resources that are better suited for a more flexible and customizable infrastructure. Here are some considerations: 1. **Resource Requirements**: Liferay DXP typically requires significant memory, CPU, and storage resources. Azure App Service, being a Platform-as-a-Service (PaaS) offering, might not provide the necessary resource flexibility and control needed for optimal performance of Liferay DXP. 2. **Custom Configuration**: Liferay DXP often needs custom configurations and tuning, which are easier to manage on Infrastructure-as-a-Service (IaaS) offerings like Azure Virtual Machines or Azure Kubernetes Service (AKS). These services provide greater control over the operating system, middleware, and application layers. 3. **Database Requirements**: Liferay DXP require...
Read more

What Azure Infrastructure is better for Liferay DXP

 When choosing between Azure Container Apps (ACA) and Azure Kubernetes Service (AKS) for Liferay DXP installations, it's important to consider the specific requirements and characteristics of your deployment. Here's a comparison to help you decide: ### Azure Container Apps (ACA) **Pros:** 1. **Simplicity**: ACA provides a serverless environment for deploying containerized applications. It abstracts away much of the underlying infrastructure management. 2. **Cost-Effective**: ACA can be more cost-effective for smaller applications or less complex deployments due to its pay-per-use pricing model. 3. **Ease of Use**: ACA is designed to be easy to use, with less complexity in setup and management compared to AKS. **Cons:** 1. **Limited Control and Flexibility**: ACA abstracts much of the infrastructure, which means you have less control over the configurations and fine-tuning of the environment. 2. **Scalability**: While ACA does support scaling, it may not handle very large or com...
Read more