Author name: YoungIT

How did I achieve my ‘Liferay DXP 7.4 Frontend Developer Certification’ ?

Uncategorized /

Few weeks back I worked on My ‘Liferay DXP 7.4 Backend Certification’ and successfully completed the same . Continuing the Learning process I took the other available certification with Liferay this week i.e. ‘Liferay DXP 7.4 Frontend Developer Certification’ and got through it with flying colours .

Why is Liferay Certification Important ? – There are a number of reasons why I feel certification is important for a Liferay Professional . Certification demonstrates your commitment to superior professionalism, upholding industry standards, and continued learning. These merits can help boost your professional credibility and prestige within your own network, organisation , customers , and when pursuing new business opportunities or bidding on projects . Not only this but it also helps us fill some gaps , It helps us understand what topics Liferay as an organisation feels are important or essential for a Liferay professional to learn . Often it happens that we may be having good knowledge on a few topics and other topics are completely ignored , this is very normal to any professional so a certification exam gives us a better idea on what all topics we should essentially touch base upon .

Certifications as per your expertise / interests – Liferay offers separate certifications in Backend development and Frontend development . You can always choose a certification where you want to demonstrate your capability . For a Full-Stack Liferay Developer I recommend taking both . Although I feel that there should also be another certification for Architects, but as of now Liferay doesn’t offer that option .

Topics-mappings for backend certification – I have tried to organise the Snapshots of important pages in a learnings Folder structure . ( You can find them in the attached shared link )

 

Shared Link : https://1drv.ms/f/s!Am4b46XblPE4h7kVo5MLibTSUswpqQ?e=6wbzxu

Set a Target Date, it helps !! – I feel that learning about any platform is something continuous and incremental in nature . It’s always better to give a logical milestone to the learning process and what better then getting certified in Liferay DXP , hence I decided to set a target a date and book my exam at https://www.webassessor.com/ . This helped me in terms of setting the goal and making the plan accordingly .

How did I achieve my ‘Liferay DXP 7.4 Frontend Developer Certification’ ? Read More »

What Customers wants the most in their B2B Portals ?

What Customers wants the most in their B2B Portals ?

Ios, Mobile /

In a B2B portal, customers typically have specific expectations and requirements that revolve around improving their business processes, enhancing efficiency, and delivering a seamless experience. While the specific needs can vary depending on the industry and organization, here are some common features and functionalities that customers often prioritize in their B2B portals:

1. User-Friendly Interface: Customers expect an intuitive and easy-to-navigate interface that allows them to quickly find the information and tools they need. A clean and organized design with logical navigation helps enhance user experience.

2. Self-Service Capabilities: B2B customers often prefer self-service options that enable them to independently access product catalogs, place orders, track shipments, manage invoices, view order history, and handle other transactions without the need for manual intervention.

3. Personalization: Customers appreciate personalized experiences tailored to their specific needs. Customization options such as saved preferences, personalized recommendations, and relevant content based on their previous interactions can significantly enhance their satisfaction and efficiency.

4. Product Information and Catalog Management: Accurate and up-to-date product information, including descriptions, specifications, pricing, availability, and images, is crucial for B2B customers. Advanced search and filtering capabilities to quickly locate products within large catalogs are also essential.

5. Order Management and Tracking: Customers expect a robust order management system that allows them to create and manage orders, track order status in real-time, view order history, request quotes, and manage returns or exchanges easily.

6. Pricing and Contract Management: B2B customers often have specific pricing agreements, contracts, and negotiated discounts. The portal should provide visibility into contract terms, personalized pricing, volume discounts, and the ability to manage contract renewals and negotiations.

7. Inventory and Stock Availability: Real-time inventory visibility helps customers determine product availability, expected delivery times, backorders, and substitutes. This information allows them to make informed decisions and plan their procurement accordingly.

8. Collaboration and Communication Tools: B2B portals that offer collaboration features such as secure messaging, document sharing, and project management capabilities enable effective communication and collaboration between customers, suppliers, and partners.

9. Integration with Backend Systems: Integration with the customer’s ERP, CRM, or other backend systems ensures seamless data flow, reduces manual data entry, and provides real-time information across the organization’s ecosystem.

10. Responsive and Mobile-Friendly Design: With the growing use of mobile devices, customers expect B2B portals to be accessible and optimized for mobile use. Responsive design ensures a consistent experience across different devices.

It’s important to note that customer preferences may vary depending on the specific industry, company size, and target audience. Conducting customer research, gathering feedback, and continuously iterating on the portal’s features based on customer needs and expectations can lead to a more successful B2B portal implementation.

 

What Customers wants the most in their B2B Portals ? Read More »

Best Practices : When using React with Liferay DXP

Best Practices : When using React with Liferay DXP

Ios, Mobile /

React has been a popular platform which has been in demand now a days .

React is popular for several reasons, which have contributed to its widespread adoption among developers:

  1. Efficiency and Performance: React’s virtual DOM and efficient rendering algorithms make it highly performant. Component Reusability: React’s component-based architecture promotes reusability, allowing developers to create modular and independent components.
  2. Declarative Syntax: React uses a declarative syntax, which means developers describe what they want the UI to look like based on the current state.
  3. Large Ecosystem and Community: React has a thriving ecosystem with a wide range of libraries, tools, and resources available.
  4. React Native: React Native, built on top of React, allows developers to build mobile applications using JavaScript.
  5. Backed by Facebook and Community Trust: React was developed by Facebook, one of the world’s leading technology companies. Its association with a major industry player has instilled trust and confidence in React’s stability, reliability, and ongoing support. The backing of Facebook, along with the active community and continuous development, has solidified React’s position as a reliable and widely adopted technology.
  6. Ease of Learning and Adoption: React has a gentle learning curve compared to other frameworks, making it accessible to developers of various skill levels.
  7. Compatibility and Integration: React can be easily integrated with other libraries and frameworks.

Different ways of React and Liferay DXP Integration

Liferay provides 3 major ways how  React can be used with it . Following are the 3 ways

  1. Adapting the SPA into a single Widget
  2. Connecting the External React Apps with Liferay Headless APIs
  3. Extracting React components into different Liferay Widgets

Different scenarios when each integration way can be used

Following are the various scenarios when you can use each method of Integration.

  1. Adapting the SPA into a single Widget – This is the easiest way of integration of React Applications within Liferay DXP . Advantages of this method is that its very simple to integrate as we could add the external React application as a Remote app within a single widget of Liferay . Disadvantage being it may not be very Design friendly and Flexibility in terms of UI is reduced drastically
  2. Connecting the External React Apps with Liferay Headless APIs – This method of integration could be used when the requirement is to use an existing or external React application need to use the Liferay DXP platform and its features. For example we need an independent React application to use the Liferay User accounts data for login and then may be to read and updates the CMS data .
  3. Extracting React components into different Liferay Widgets – While this way may be the best way of integration in terms of Design and Flexibility but it may be a Labor Intensive process. In this process the react components can be divided logically into components which could be displayed individually in different widgets . This gives good presentability and the most preferred way for a complex applications .

 

Best Practices : When using React with Liferay DXP Read More »

Architecture and Solutioning Series: Persisting Bearer Token Using Liferay DXPs Expendo Table Feature

Architecture and Solutioning Series: Persisting Bearer Token Using Liferay DXPs Expendo Table Feature

Android, Mobile /

Problem statement:

In this particular Scenario in the existing application the SSO was implemented using Microsoft OIDC Provider with Liferay DXP. At the time of login the ‘Microsoft OIDC provider’ generated a Bearer Token which was the identifier for the authenticated user .

This Bearer token was needed for all the further API calls to the API Gateway (which in turn called the external data source) . The API gateway used the Bearer Token to further validate the users identity and once validated it Processed the appropriate API response to the API call request .Hence we need to make it available throughout . We were not allowed to save the Token in Sessions because of security reasons.

Swim-lane diagram showing the OpenID Connect protocol's sign-in flow.

Reference : https://learn.microsoft.com/en-us/azure/active-directory/develop/v2-protocols-oidc

Conditions:

Bearer Token is Unique to every login .

Bearer Token is only available while OIDC call while login

Bearer Token should be available for the whole logged in period

Solution:

  1. We planned to extract the Bearer token  at the Login time Once at the while SSO event .
  2. To do so we used Liferay Post Login Action Feature to catch the event .
  3. We Extracted the TOKEN using logic local to the application .
  4. We decided to use Expendo Table feature and stored in KEY – VALUE where USERID was KEY and TOKEN was VALUE
  5. This KEY – VALUE was UNIQUE to each user and each login .



Following is the Example Code snippet for the same.

package com.login.event.post;
import com.liferay.expando.kernel.model.ExpandoTableConstants;
import com.liferay.expando.kernel.service.ExpandoValueLocalServiceUtil;
import com.liferay.portal.kernel.events.ActionException;
import com.liferay.portal.kernel.exception.PortalException; 
import com.liferay.portal.kernel.model.User; 
import com.liferay.portal.kernel.service.UserLocalServiceUtil;
import com.liferay.portal.kernel.events.LifecycleAction;
import com.liferay.portal.kernel.events.LifecycleEvent;
import org.osgi.service.component.annotations.Component;
/**
 * 
 * --------Author Details---------
 * Name:    YoungIT Consulting Services GmbH
 * Email:   [email protected]
 * Address: Fleethörn 7, 24103 Kiel, Germany
 * Phone:   +491514 5682025
 * --------Author Details---------
 * 
 */
@Component
(
immediate = true,
property = { "key=login.events.post" },
service = LifecycleAction.class
)
public class LoginPostAction implements LifecycleAction {
    @Override
    public void processLifecycleEvent(LifecycleEvent lifecycleEvent) throws ActionException {
        long userId = Long.parseLong(lifecycleEvent.getRequest().getUserPrincipal().toString());
        User user;
        try {
            user = UserLocalServiceUtil.getUser(userId);
            ExpandoValueLocalServiceUtil.addValue(user.getCompanyId(), User.class.getName(), ExpandoTableConstants.DEFAULT_TABLE_NAME,
                    "bearerToken", user.getPrimaryKey(), "==UPDATE_TOKEN_HERE==");
        } catch (PortalException e) {
            // TODO Auto-generated catch block
            e.printStackTrace();
        }
        System.out.println("login.event.pre=" + lifecycleEvent);
    }

Architecture and Solutioning Series: Persisting Bearer Token Using Liferay DXPs Expendo Table Feature Read More »

SSO Architecture using OpenID Connect (OIDC) protocol with Liferay DXP

SSO Architecture using OpenID Connect (OIDC) protocol with Liferay DXP

Liferay portal /
In continuation with my last article on SSO i.e. (https://lnkd.in/eFEYSpqg) , I created a 40 sec flow diagram video .
This Flow diagram illustrate SSO Flow using OpenID Connect (OIDC) protocol with Liferay DXP Portal.

Following are the steps .


Step 1) User request SignIn page using browser , SignIn Page Open up , User clicks on the SignIn Link.

Step 2) Liferay redirects to the SignIn page (called Authorization Endpoint)of the OIDC Provider screen (Provider could be Microsoft azure ,google or any other provider).

Step 3) User enters the credentials.

Step 4) OIDC Provider process the request and generate a Token and sends back to the user browser.

Step 5) Browser redirect the request to Liferay Redirect URI along with the Token.

Step 6) Liferay Validates the token using Providers JWKS URI which contains the public keys that can verify the token. Once token Validation is successful Liferay adds a session cookie on to the browser which to keeps the session with the browser alive .

#datasecurity #singlesignon  #liferay #liferaydxp #liferayExperienceCloud #architecture #SSO #saml #openid #saml  #oidc  #design

 

 

SSO Architecture using OpenID Connect (OIDC) protocol with Liferay DXP Read More »

Liferay ODER WordPress für mein Geschäftsportal: Wann verwende ich sie und was ist der Unterschied?

Liferay ODER WordPress für mein Geschäftsportal: Wann verwende ich sie und was ist der Unterschied?

web development /

Liferay und WordPress sind beliebte Plattformen für die Erstellung von Websites und die Verwaltung digitaler Inhalte, weisen jedoch deutliche Unterschiede hinsichtlich ihrer Zielgruppe, Funktionalität und Flexibilität auf. Hier ist ein Vergleich zwischen Liferay und WordPress:

Zielgruppe (Target audience)

Liferay: Liferay DXP richtet sich in erster Linie an Unternehmen und große Organisationen, die eine umfassende Digital-Experience-Plattform zum Aufbau komplexer und skalierbarer Websites, Intranets und Portale benötigen. Es richtet sich an Unternehmen mit unterschiedlichen Anforderungen an Content-Management und Zusammenarbeit.

WordPress: WordPress wird häufig von Einzelpersonen, kleinen Unternehmen und Bloggern verwendet, die eine benutzerfreundliche und anpassbare Plattform zum Erstellen von Websites und Veröffentlichen von Inhalten benötigen. Es eignet sich eher für einfachere Websites und bietet nicht die gleichen Funktionen auf Unternehmensebene wie Liferay.

Funktionalität und Features:

Liferay: Liferay DXP bietet eine breite Palette an Funktionen für Content-Management, Zusammenarbeit, Personalisierung und Integration. Es bietet robustes Workflow-Management, rollenbasierte Zugriffskontrolle, Tools für die soziale Zusammenarbeit und mehrsprachige Unterstützung. Liferay DXP ist für die Bewältigung komplexer Unternehmensanforderungen konzipiert und unterstützt die Integration mit verschiedenen Systemen.

WordPress: WordPress ist für seine Einfachheit und Benutzerfreundlichkeit bekannt. Es bietet wichtige Content-Management-Funktionen, eine umfangreiche Bibliothek mit Plugins und Themes zur individuellen Anpassung sowie eine große Entwickler-Community. Obwohl WordPress über eine breite Palette an Plugins verfügt, die seine Funktionalität erweitern, bietet es möglicherweise nicht das gleiche Maß an Funktionen der Enterprise-Klasse wie Liferay.

Flexibilität und Anpassung:

Liferay: Liferay DXP bietet eine äußerst flexible und erweiterbare Plattform. Es bietet eine modulare Architektur, die es Entwicklern ermöglicht, benutzerdefinierte Anwendungen, Themes und Erweiterungen zu erstellen. Liferay DXP kann auf spezifische Geschäftsanforderungen zugeschnitten und in bestehende Systeme integriert werden. Allerdings erfordert die Anpassung in Liferay im Vergleich zu WordPress möglicherweise mehr technisches Fachwissen.

WordPress: WordPress ist bekannt für seine Flexibilität und umfangreichen Anpassungsmöglichkeiten. Es bietet ein umfangreiches Ökosystem an Plugins und Themes, mit denen Benutzer problemlos Funktionen hinzufügen und das Design ihrer Websites ändern können. WordPress bietet eine benutzerfreundliche Oberfläche, die es auch technisch nicht versierten Benutzern für grundlegende Anpassungen zugänglich macht.

Skalierbarkeit

Liferay: Liferay DXP ist für die Bewältigung großer Unternehmensanforderungen konzipiert. Es unterstützt hohe Datenverkehrsvolumina, bietet Clustering- und Lastausgleichsfunktionen und kann an wachsende Anforderungen angepasst werden. Liferay DXP eignet sich für Organisationen mit komplexen und hoch skalierbaren digitalen Plattformen.

WordPress: WordPress kann eine beträchtliche Menge an Datenverkehr verarbeiten, erfordert jedoch möglicherweise zusätzliche Optimierungs- und Caching-Mechanismen für Websites mit hohem Datenverkehr. Während WordPress für kleine und mittlere Unternehmen geeignet sein kann, ist es für Unternehmensanforderungen möglicherweise nicht so robust oder skalierbar wie Liferay.

Unterstützung und Community

Liferay: Liferay DXP bietet Support auf Unternehmensniveau und verfügt über ein engagiertes Support-Team, das Kunden unterstützt. Es verfügt außerdem über eine aktive Community von Entwicklern und Benutzern, die zur laufenden Entwicklung beitragen und über Foren und Online-Ressourcen Unterstützung bieten.

WordPress: WordPress verfügt über eine riesige Community von Benutzern und Entwicklern weltweit. Es verfügt über umfangreiche Dokumentation, Foren und Online-Ressourcen, sodass Sie leicht Antworten auf häufige Fragen finden können. Offizieller Support für WordPress erfolgt jedoch in der Regel über kostenpflichtige Dienste oder Drittanbieter.

Zusammenfassend lässt sich sagen, dass Liferay und WordPress unterschiedliche Zielgruppen ansprechen und unterschiedliche Stärken haben. Liferay DXP ist eine robuste Plattform auf Unternehmensebene mit umfassenden Funktionen für Content-Management, Zusammenarbeit und Integration. WordPress hingegen ist eine benutzerfreundliche Plattform mit einem umfangreichen Plugin- und Theme-Ökosystem und eignet sich daher ideal für Einzelpersonen, kleine Unternehmen und Blogger, die Wert auf Einfachheit und Anpassung legen.

 

Sicherheitsvergleich beider Plattformen

Im Allgemeinen ist der Vergleich der Sicherheit von Liferay und WordPress nicht einfach, da Sicherheit ein komplexes und vielschichtiges Thema ist, das von verschiedenen Faktoren abhängt, darunter der Plattform selbst, ihrer Konfiguration, Wartungspraktiken und dem Benutzerverhalten. Im Hinblick auf die Sicherheit in Liferay und WordPress sind jedoch einige Punkte zu beachten:

Liferay:

  1. Unternehmensfokus: Liferay DXP ist auf Sicherheit auf Unternehmensniveau ausgelegt. Es bietet robuste Zugriffskontrollmechanismen, rollenbasierte Berechtigungen und umfangreiche Authentifizierungsoptionen, sodass Unternehmen Sicherheitsrichtlinien effektiv durchsetzen können.
  2. Regelmäßige Updates und Sicherheitspatches: Liferay verfügt über ein spezielles Sicherheitsteam, das regelmäßig Updates und Sicherheitspatches veröffentlicht, um Schwachstellen zu beheben und die Sicherheit der Plattform zu verbessern. Wenn Sie über die neuesten Versionen auf dem Laufenden bleiben, können Sie sicherstellen, dass Sicherheitskorrekturen angewendet werden.
  3. Starke Benutzerverwaltung: Liferay DXP bietet erweiterte Benutzerverwaltungsfunktionen, einschließlich fein abgestimmter Berechtigungskontrollen und Benutzerauthentifizierungsoptionen wie LDAP-Integration und Single Sign-On (SSO). Diese Funktionen tragen zu einer sichereren Benutzerumgebung bei.

WordPress:

  1. Popularität und Plugins von Drittanbietern: Die Popularität von WordPress macht es zu einem häufigen Ziel von Angriffen. Allerdings wird die Kernsoftware von WordPress selbst regelmäßig aktualisiert, um Sicherheitslücken zu schließen. Die Sicherheit von WordPress kann durch die Verwendung von Plugins und Themes von Drittanbietern beeinflusst werden, da deren Qualität und Sicherheitspraktiken variieren. Es ist wichtig, seriöse und regelmäßig gewartete Plugins aus vertrauenswürdigen Quellen auszuwählen.
  2. Sicherheits-Plugins und Best Practices: WordPress bietet eine Reihe von Sicherheits-Plugins, die die Sicherheit der Plattform verbessern können, wie zum Beispiel Firewall-Plugins, Malware-Scanner und Anmeldeschutz. Auch die Einhaltung bewährter Sicherheitspraktiken, wie die Verwendung sicherer Passwörter, die regelmäßige Aktualisierung von Plugins und Themes sowie die Implementierung von sicherem Hosting, kann die Sicherheit von WordPress erheblich verbessern.
  3. Community und Support: Die große WordPress-Community überwacht aktiv Sicherheitsprobleme und trägt zur kontinuierlichen Entwicklung und Verbesserung der Sicherheit der Plattform bei. Darüber hinaus stellt WordPress.org Ressourcen und Richtlinien zu bewährten Sicherheitspraktiken bereit, um Benutzern beim Schutz ihrer Websites zu helfen.

Zusammenfassend lässt sich sagen, dass sowohl Liferay als auch WordPress durch die richtige Konfiguration, Wartung und Einhaltung bewährter Sicherheitspraktiken sicher gemacht werden können. Während Liferay DXP über Sicherheitsfunktionen der Enterprise-Klasse und ein engagiertes Sicherheitsteam verfügt, kann die Sicherheit von WordPress durch die Verwendung seriöser Plugins, regelmäßige Updates und verantwortungsvolle Benutzerpraktiken verbessert werden. Es ist wichtig, wachsam zu bleiben, Sicherheitsupdates umgehend anzuwenden und empfohlene Sicherheitspraktiken zu befolgen, um Risiken zu mindern und die Sicherheit jeder Plattform zu gewährleisten.

 

 

Liferay ODER WordPress für mein Geschäftsportal: Wann verwende ich sie und was ist der Unterschied? Read More »

Understanding SSO – Part 1

Understanding SSO – Part 1

Mobile, React /

Understanding SSO concepts

To better understand SSO we first understand the evolution of authentication .

1) Simple authentication architecture (Without SSO)

 

  • There is a client (who is using the browser).
  • There is a server (which is basically a web server for the application) .
  • Client calls the login page and enters the Credentials .
  • Server authenticates the credentials again the DB .
  • Once authentication succeeds a session cookies is established between the client and server .

2) Generic SSO architecture

 

 

  1. The First call made to the web-application is redirected to the Identity provider (IdP) login page.
  2. User enters the credentials via browser and get back the token from the Identity provider (IdP).
  3. Token is sent to the Web application .
  4. Web app had a trust relationship with Idp or can have a key from Identity Provider (IdP) which is used to check the validity of the token.
  5. Once the validation succeeds the Web application puts a session cookie on the browser and the connection is established .

3) Understanding the Protocols

Now since we have understood the basic SSO mechanism , now is the time to get an understanding of the underlying authentication protocols used .

whenever we talk SSO we quite often hear about SAML , Open ID Connect , OAuth2 , OIDC etc.

Lets try to understand these

  • First thing first we need to understand that Open ID Connect and OIDC are the same protocol , so let’s not confusion over that .
  • Second important point is While OAuth 2.0 is an authorization protocol, OIDC is an identity authentication protocol .
  • Third point we need to know is The OpenID Connect (OIDC) protocol is built over the OAuth 2.0 protocol and helps authenticate users and convey information about them .
  • SAML is XML based and OIDC is JSON based protocol
  • SAML is quite old is Industry hence is quite matured but at the same time Complex .
  • SAML has highest security standard where as OIDC is moderate
  • OIDC is top in sense of user friendliness and implementations

So I hope you got the gist now i.e. SAML and OIDC can be used for identity authentication. These 2 protocols hence are also used for SSO implementations .

4) Differences between SAML and OIDC

 

 

Stay tuned to check more about SSO in our next article…

Understanding SSO – Part 1 Read More »

GraphQL in Liferay DXP

GraphQL in Liferay DXP

UI/UX /

 

Checkout the flow diagram here 

What is GraphQL ?

GraphQL is basically a query language to read or mutate data in API . In simple words its a way to call API for read and write purpose using query like syntax . Using GraphQL feels like you are querying an API service instead of a database . This was developed by Facebook .

Challenges with REST

REST API calls has lot of advantages which is well known to developers but at the same time there are few drawbacks which REST API calls doesn’t address . Lets talk about few of them

Over fetching: This is when the API endpoint provides way more information than required by the client.

Under fetching: This is when the API endpoint doesn’t provide all of the required information. So, the client has to make multiple requests (API Calls) to get everything the application needs.

When to use GraphQL ?

 

Architectural Scenarios

  • While writing code for mobile devices, smartwatches, and IOT Platforms , where bandwidth usage is critical parameter.
  • Application requirements where nested data needs to be fetched in a single call ( For example a case when we need USER details then PRODUCTS details bought by USER ).
  • A composite pattern, where an application retrieves data from multiple, different storage APIs.

 

How to use GraphQL in Liferay ?

Liferay by default comes with Out of the box List of APIs which you can access

  1. First Login as Admin
  2. Use the same browser to call the following URL
http://[host]:[port]/o/api

For example, if you’re running Liferay DXP locally on port 8080, the URL for discovering the GraphQL API is

3) Once you are on this page you can click GraphQL link on the top Right of the page

Example to Read

Here are steps to read all the blog content through GraphQL API

  1. Login as Admin
  2. Hit the URL http://localhost:8080/o/api
  3. Go to Graphql Tab
  4. write the Following query

query

{

blogPostings(filter:””,page:1,pageSize:10,search:””,siteKey:”47311″,sort:””)

{

page

items

{

id

headline

creator

{

name

}

}

}

}

Get the siteKey from Site configuration page of the site as shown in the Image 3 and replace in your query. If you have any blogs in that site then the query will give back some results else you can do the next step (To enter a blog entry via API) First and then retry this query again to get back some results . In my case since I had an entry you can see the API output on the Right hand side in the screenshot .

Image 1

Image 2

Example to Mutate (Write)

Here are steps to read all the blog content through GraphQL API

  1. Login as Admin
  2. Hit the URL http://localhost:8080/o/api
  3. Go to Graphql Tab
  4. write the Following query

mutation CreateBlog($blog: InputBlogPosting)

{

createSiteBlogPosting(blogPosting: $blog, siteKey: “47311” )

{

headline

articleBody

id

friendlyUrlPath

}

}

}

In the Query Variables you can enter the entry like following

{

“blog”:

{

“articleBody”: “Contact us for EU based Liferay Consultants at Liferayconsulting.com !”,

“headline”: “Liferayconsulting.com”

}

}

now run the query and the API call to write or mutate is done . You can now rerun the read query to find your entry appearing there .

Diagram Links

GraphQL in Liferay DXP Read More »

Moduler Approach in Liferay DXP

Moduler Approach in Liferay DXP

Android, Mobile /

 

1) How moduler approach in Liferay helps creating customized solutions.

2) Liferay can be better explained as set of cubes where each cube is a different feature .

3) Customizing the vanilla (Default) Liferay Bundle by simply ADDING or REMOVING these cubes (Features).

4) Enabling/ disabling Multiple (OOB) security features as per customers need .( Example – Enabling SSO with NTLM, CAS, SiteMinder, OpenSSO, OpenID, Facebook)

5) Scaling the solution as per expected number of enduser (can be achieved using features like autoscaling in LIferay DXP Cloud ).

Link – https://lnkd.in/eWZHmtgc
#architect #security #cloud #Liferay #liferaydxp
#digital #experience  #liferayExperienceCloud #architecture  #design

 

Moduler Approach in Liferay DXP Read More »

Liferay vs WordPress : When to use and What is the difference ?

Liferay vs WordPress : When to use and What is the difference ?

Liferay, wordpress /

Liferay and WordPress are both popular platforms for building websites and managing digital content, but they have distinct differences in terms of their target audience, functionality, and flexibility. Here’s a comparison between Liferay and WordPress:

  1. Target Audience:
    • Liferay: Liferay DXP primarily targets enterprises and large organizations that require a comprehensive digital experience platform to build complex and scalable websites, intranets, and portals. It caters to businesses with diverse content management and collaboration needs.
    • WordPress: WordPress is widely used by individuals, small businesses, and bloggers who need a user-friendly and customizable platform to create websites and publish content. It is more suited for simpler websites and does not offer the same enterprise-level features as Liferay.
  2. Functionality and Features:
    • Liferay: Liferay DXP provides a wide range of features for content management, collaboration, personalization, and integration. It offers robust workflow management, role-based access control, social collaboration tools, and multilingual support. Liferay DXP is designed to handle complex enterprise requirements and supports integrations with various systems.
    • WordPress: WordPress is known for its simplicity and ease of use. It offers essential content management features, a vast library of plugins and themes for customization, and a large community of developers. While WordPress has a broad range of plugins that extend its functionality, it may not provide the same level of enterprise-grade features as Liferay.
  3. Flexibility and Customization:
    • Liferay: Liferay DXP provides a highly flexible and extensible platform. It offers a modular architecture that allows developers to build custom applications, themes, and extensions. Liferay DXP can be tailored to specific business needs and integrated with existing systems. However, customization in Liferay may require more technical expertise compared to WordPress.
    • WordPress: WordPress is renowned for its flexibility and extensive customization options. It offers a vast ecosystem of plugins and themes, allowing users to add functionality and change the design of their websites easily. WordPress provides a user-friendly interface, making it accessible to non-technical users for basic customization.
  4. Scalability:
    • Liferay: Liferay DXP is designed to handle large-scale enterprise requirements. It supports high traffic volumes, provides clustering and load balancing capabilities, and can scale to accommodate growing needs. Liferay DXP is suitable for organizations with complex and highly scalable digital platforms.
    • WordPress: WordPress can handle a significant amount of traffic but may require additional optimization and caching mechanisms for high-traffic websites. While WordPress can be suitable for small to medium-sized businesses, it may not be as robust or scalable as Liferay for enterprise-level needs.
  5. Support and Community:
    • Liferay: Liferay DXP offers enterprise-grade support and has a dedicated support team that provides assistance to customers. It also has an active community of developers and users who contribute to its ongoing development and provide support through forums and online resources.
    • WordPress: WordPress has a vast community of users and developers worldwide. It has extensive documentation, forums, and online resources, making it easy to find answers to common questions. However, official support for WordPress is typically provided through paid services or third-party providers.

In summary, Liferay and WordPress cater to different audiences and have distinct strengths. Liferay DXP is a robust enterprise-level platform with comprehensive features for content management, collaboration, and integration. WordPress, on the other hand, is a user-friendly platform with a vast plugin and theme ecosystem, making it ideal for individuals, small businesses, and bloggers who prioritize simplicity and customization.

 

Security comparison of both the platforms

 

In general, comparing the security of Liferay and WordPress is not straightforward because security is a complex and multifaceted topic that depends on various factors, including the platform itself, its configuration, maintenance practices, and user behavior. However, here are some points to consider regarding security in Liferay and WordPress:

Liferay:

  1. Enterprise Focus: Liferay DXP is designed with enterprise-level security in mind. It offers robust access control mechanisms, role-based permissions, and extensive authentication options, allowing organizations to enforce security policies effectively.
  2. Regular Updates and Security Patches: Liferay has a dedicated security team that regularly releases updates and security patches to address vulnerabilities and enhance the platform’s security. Staying up to date with the latest versions helps ensure that security fixes are applied.
  3. Strong User Management: Liferay DXP provides advanced user management features, including fine-grained permission controls and user authentication options such as LDAP integration and single sign-on (SSO). These features contribute to a more secure user environment.

WordPress:

  1. Popularity and Third-Party Plugins: WordPress’s popularity makes it a frequent target for attacks. However, the core WordPress software itself is regularly updated to address security vulnerabilities. The security of WordPress can be influenced by the use of third-party plugins and themes, as their quality and security practices vary. It is important to choose reputable and regularly maintained plugins from trusted sources.
  2. Security Plugins and Best Practices: WordPress offers a range of security plugins that can enhance the platform’s security, such as firewall plugins, malware scanners, and login protection. Adhering to security best practices, such as using strong passwords, regularly updating plugins and themes, and implementing secure hosting, can also significantly improve WordPress security.
  3. Community and Support: The large WordPress community actively monitors security issues and contributes to the ongoing development and improvement of the platform’s security. Additionally, WordPress.org provides resources and guidelines on security best practices to help users protect their websites.

In conclusion, both Liferay and WordPress can be made secure with proper configuration, maintenance, and adherence to security best practices. While Liferay DXP has enterprise-grade security features and a dedicated security team, WordPress’s security can be enhanced through the use of reputable plugins, regular updates, and responsible user practices. It is essential to stay vigilant, apply security updates promptly, and follow recommended security practices to mitigate risks and ensure the security of any platform.

Liferay vs WordPress : When to use and What is the difference ? Read More »

Language
Scroll to Top