Tuesday, April 3, 2012
Security System in Liferay
Here’s a brief outline of how you can use your own security system in Liferay.
• Create your own PermissionChecker class that extends Liferay’s PermissionChecker class.
• Register this new class in portal.properties (or portal-ext.properties for the EXT environment) under the permissions.checker property.
• Override the hasUserPermission(…) method and the hasGuestPermission(…) method with your
own calls to your permission system.
• You can call the setValues(…) method to pull in parameters from the request object that your permission
checker might need (e.g., userId, projected, etc).
• You can call the resetValues(…) method to wipe out old parameters.
• Override the isAdmin(…) method.
IFrame in Liferay
1. This portlet is defined in /portal-web/docroot/WEB-INF/portlet.xml.
<portlet>
<portlet-name>48</portlet-name>
<display-name>IFrame</display-name>
<portlet-class>com.liferay.portlet.IFramePortlet</portlet-class>
<expiration-cache>0</expiration-cache>
<supports>
<mime-type>text/html</mime-type>
<portlet-mode>edit</portlet-mode>
</supports>
<resource-bundle>com.liferay.portlet.StrutsResourceBundle</resource-bundle>
<portlet-preferences>
<preference>
<name>src</name>
<value>http://www.gfa.org</value>
</preference>
<preference>
<name>auth</name>
<value>false</value>
</preference>
<preference>
<name>auth-type</name>
<value>basic</value>
</preference>
<preference>
<name>form-method</name>
<value>post</value>
</preference>
<preference>
<name>user-name</name>
<value></value>
</preference>
<preference>
<name>password</name>
<value></value>
</preference>
<preference>
<name>hidden-variables</name>
<value>var1=hello;var2=world</value>
</preference>
</portlet-preferences>
<security-role-ref>
<role-name>Power User</role-name
</security-role-ref>
<security-role-ref>
<role-name>User</role-name>
</security-role-ref>
</portlet>
The unique id associated with this portlet is 48. The IFramePortlet class extends javax.portlet.GenericPortlet.
The source [http://content.liferay.com/document/api/portal-ejb/com/liferay/portlet/IFramePortlet.java.html] of
this class shows that this class prints an IFRAME tag that references an external site. This portlet is editable
and viewable by HTML browsers. The preferences bind the name src with the default value of http://www.gfa.org.
The auth value, if set to true, will attempt to authenticate the user to the external IFrame application. The authtype value can be set to basic or form. Basic authentication appends the login information to the URL and form
authentication requires a post to the external IFrame application. The form-method value can be set to get or
post. This is only used if you are using form authentication. The user-name value sets the user name for authentication. If you are using basic authentication, then you just need to set the user name. If using form authentication, you need to set the user name as a key value pair like acme_login=test@acme.com. The password
value sets the password for authentication. If using basic authentication, you just need the password. If using
form authentication, set the password as a key value pair like acme_password=password. The hidden-variables value is used for form authentication. Some forms require certain prepopulated fields in order to proceed
with authentication. Separate each key and value with a = and each key value pair with a ;. Users must have
either the Power User or User role to access this portlet. The roles can be changed at run time via the Admin
portlet.
2. The title is fetched by StrutsResourceBundle and is configured in /
portal-ejb/classes/content/Language.properties.
javax.portlet.title.48=IFrame
3. Additional definitions for this portlet are found in /portal-web/docroot/WEB-INF/liferay-portlet.xml.
<portlet id="48" struts-path="iframe" />
The id value in liferay-portlet.xml must match the portlet-name value in portlet.xml. The struts-path value
tells Struts that all requests starting with http://localhost/c/iframe/* are considered part of this portlet's scope.
See the Mail portlet to better understand this feature.
4. Display information for this portlet is found in /portal-web/docroot/WEB-INF/liferay-display.xml and makes it
possible for users to add this portlet via the personalize pages screen.
<category name="category.test">
<portlet id="47" />
<portlet id="48" />
</category>
When a user goes to personalize pages and clicks on a category to choose a portlet, the IFrame portlet is available under the category with the name that matches the key category.test. The value for this key is defined in /
portal-ejb/classes/content/Language.properties.
category.test=Test
Calendar in Liferay
1. This portlet is defined in /portal-web/docroot/WEB-INF/portlet.xml.
<portlet>
<portlet-name>8</portlet-name>
<display-name>Calendar</display-name>
<portlet-class>com.liferay.portlet.JSPPortlet</portlet-class>
<init-param>
<name>view-jsp</name>
<value>/portlet/calendar/view.jsp</value>
</init-param>
<expiration-cache>0</expiration-cache>
<supports>
<mime-type>text/html</mime-type>
</supports>
<resource-bundle>com.liferay.portlet.StrutsResourceBundle</resource-bundle>
<security-role-ref>
<role-name>Power User</role-name>
</security-role-ref>
<security-role-ref>
<role-name>User</role-name>
</security-role-ref>
</portlet>
The unique id associated with this portlet is 8. The JSPPortlet class extends javax.portlet.GenericPortlet. The
source of this class shows that this class looks for the init parameters and forwards to the appropriate JSP depending on the portlet mode. This portlet is viewable by HTML browsers. Users must have either the Power
User or User role to access this portlet. The roles can be changed at run time via the Admin portlet.
2. The title is fetched by StrutsResourceBundle and is configured in /
portal-ejb/classes/content/Language.properties.
javax.portlet.title.8=Calendar
3. Additional definitions for this portlet are found in /portal-web/docroot/WEB-INF/liferay-portlet.xml.
<portlet
id="8"
struts-path="calendar"
scheduler-class="com.liferay.portlet.calendar.job.Scheduler"
preferences-sharing-type="user"
show-portlet-access-denied="true"
show-portlet-inactive="true"
</
The id value in liferay-portlet.xml must match the portlet-name value in portlet.xml. The struts-path value tells
Struts that all requests starting with http://localhost/c/calendar/* are considered part of this portlet's scope. See
the Mail portlet to better understand this feature. The scheduler-class value must be a class that implements
Scheduler and is called to schedule Quartz jobs for this portlet. The preferences-sharing-type value indicates
the preferences sharing type of the portlet. If set to none, preferences are not shared and each page will have its
own set of preferences. If set to user, preferences are shared by user if the portlet is in a personal page or by
group if the portlet is in a group page. If set to company, preferences are shared across the entire company. The
show-portlet-access-denied value, if set to true, means non-permissioned users are shown that they do not have
access to the portlet. The default value is set in portal.properties. The show-portlet-inactive value, if set to true,
means users are shown that the portlet is inactive (if the portlet is inactive). The default value is set in
portal.properties
4. Display information for this portlet is found in /portal-web/docroot/WEB-INF/liferay-display.xml and makes it
possible for users to add this portlet via the personalize pages screen.
<category name="category.community">
...
<portlet id="8" />
...
</category>
When a user goes to personalize pages and clicks on a category to choose a portlet, the Calendar portlet is
available under the category with the name that matches the key category.community. The value for this key is
defined in /portal-ejb/classes/content/Language.properties.
category.community=Community
Code Conventions in Liferay
We are proud and passionate about super clean code. Wrap lines at 80 spaces and use real tabs equivalent to 4spaces. Follow the Java Code Conventions and read
The Elements of Java Style. And ABOVE all else, follow thprecedence of the rest of the code.
The Elements of Java Style. And ABOVE all else, follow thprecedence of the rest of the code.
Liferay with Groovy
Liferay with ruby
Liferay with PHP
Liferay with Groovy
Liferay with PHP
Liferay with Groovy
- We can create Groovy, Ruby or PHP portlets and use them with Liferay
- Liferay plugins repository has several examples of these
Liferay supports Web Services
Title: Web services in Liferay
• JSON
• Hessian
• Burlap
• REST
*RMI
• Spring HTTP
• WSRP
• WebDAV
Performance in Liferay
- Multi-tier clustering at any combination of multiple tiers(presentation, service, business logic, and database)
- Advanced Caching
- Page Caching
- Load Balancing
- Session Replication
- Distributed Cache
- Static Content Export
- Liferay Portal has been deployed to Amazon EC2 which uses virtualization and cloud computing technologies to scale dynamically to geographically specific areas of demand.
Security in Liferay
- Liferay Portal uses industry standard, governmentgrade encryption technologies including advanced algorithms such as DES, MD5 and RSA. Liferay was benchmarked as among the most secure portal platforms using LogicLibrary's Logiscan suite.
- · Pluggable Authentication
- Email Verification
- Granular Permissioning
- LDAP Authentication
- Session Management
Service Builder in Liferay
- · Liferay has very good service builder utility. We can specify our domain model in a service.xml file and run an ant task. The utility will create Java files, Hibernate files,and service classes
- Service Builder is a RAD tool, we may choose to use our own service framework and layer instead
Creating an extension environment in Liferay
Title : How to Create a extension environment in Liferay
*An extension environment can be created from Liferay portal source
*An extension environment can be created from Liferay portal source
• The ext environment gives us complete control over the way the system behaves with ways to reconfigure default Liferay behavior
• release.adave.properties
• app.server.adave.properties
• ant clean start build-ext (takes 7-8 mins)
• ant clean deploy (takes 1-2 mins)
• Configure root.xml on tomcat to connect to database
• Run the app …
Using the plugins sdk in liferay
· Plugins sdk can be used to create portlets and themes and deploy them to the Liferay portal
· Easiest and fastest way to start building the enterprise portal application
· Plugins are hot deployed to tomcat
·
· Plugins are fully JSR compliant and plugins developed outside sdk can also be used
*ant -Dportlet.name="hello-world" -Dportlet.display.name="Hello World " create
•ant -Dtheme.name="sample-theme" -Dtheme.display.name="Sample Theame “ Create
*ant deploy
Why use Liferay
- Need a portal based application
- Need rapid development and / or prototyping (Well, most projects do !)
- Need collaboration e-commerce, internationalization
Posts
