MySQL LDAP authentication plugin. LDAP Authentication module for MySQL Community Server 5.5.7 by Charalampos Serenis Copyright © 2012 Infoscope Hellas L.P.
This work is licensed under the Creative Commons Attribution License. To view a copy of this license, visit or send a letter to Creative Commons, 559 Nathan Abbott Way, Stanford, California 94305, USA. Foreword User management is one of the most common administrative tasks. Organizations are dependent on multiple resources that must be strictly regulated. Introduction Since version 5.5.7, MySQL Community Server supports user authentication through plugins. The motivation In Infoscope's development servers we needed to provide our developers access to a MySQL server. Plugin auth_ldap for MySQL Community Server Auth_ldap is an authentication plugin, for MySQL Community Server 5.5.7 that allows database administrators to reuse user accounts stored in an LDAP directory. Prerequisites. Connecting to different database using Liferay Service Builder - Blog.
Connecting to different database using Liferay Service Builder Generally when we create a Custom portlet using Service builder or use Service Builder to generate code for persistence and service/model layers.
The logic we use is persisting the data in Liferay DB .i.e... DB configured in portal-ext. properties. But in my case I had a requirement where in, Client had a separate DB schema and he wanted complete separation of logic from Liferay DB. All he needed is Crud operations on those tables. We also have requirement that Client wants there Data on Separate Schema or Separate DB.
After searching and analyzing different blogs, I came to conclusion and starting implementing them. As we are using service-builder, it means that you need code for tables other than liferay default DB. So let’s start our code with basic data model as shown below. Step 1: Service.xml : Once you run the build service, it will generate all the code required for model, service and persistence layer as shown below. Liferay vs. djangocms comparison. Scripting Language Portlets. Introduction # Liferay has support for developing portlets in Ruby, PHP, Groovy, Python, and Javascript in the plugins environment.
Developing using scripting languages is quite easy. You can use the sample portlets as reference, providing the developer the appropriated directory structure, that looks similar to Description # All the impotant files are under docroot/WEB-INF. <portlet-class>com.liferay.util.bridges.groovy.GroovyPortlet</portlet-class><init-param><name>view-file</name><value>/WEB-INF/groovy/view.groovy</value></init-param><init-param><name>action-file</name><value>/WEB-INF/groovy/action.groovy</value></init-param><init-param><name>global-files</name><value>/WEB-INF/groovy/global/LiferayPortlet.groovy,/WEB-INF/groovy/global/Custom.groovy</value></init-param> The other files (info.groovy and java.groovy) represent different views your portlet may have, but they have to be linked from somewhere to be accessible.
Django vs. Liferay - Google Groupes. Liferay vs. Django CMS usage comparison. Technologies > Content Management > Technology usage comparison Request an extensive market report of specific content management systems.
Learn more This report shows the usage statistics of Liferay vs. Django CMS as content management system on the web. See technologies overview for explanations on the methodologies used in the surveys. Usage and market share This diagram shows the percentages of websites using the selected technologies. How to read the diagram:Liferay is used by 0.1% of all the websites, that is a content management system market share of 0.2%. Usage broken down by ranking This diagram shows the percentages of websites using the selected technologies broken down by ranking.
How to read the diagram: Liferay is used by 0.2% of all the websites whose content management system we know.Liferay is used by 0.3% of all the websites whose content management system we know and that rank in the top 1,000,000. Historical trend Market position More details.