RE: [RESOLVED]: SOAP calls from PHP app + nuSOAP : data types

[Solved] Export Password and userAccountContro to Active Directory

2013-03-07T13:39:51Z

Hi community,

Since I spent hours to find out how to make it work, and to actually make it work, here is a summary about:
- exporting password to AD
- exporting user status (disabled/enabled) to AD

Tested with 6.2m3.

1. configure AD with SSL to enable LDAPS
2. import the certificate into your Tomcat (or any webapp server) JVM
3. Map Liferay password attribute to "unicodePwd", which encoding is correctly handled by Liferay
4. Set ldap password encryption to empty (ie. keep the property in portal-ext.properties without any value)
5. Create your own UserModelListener. Force ldap export when password is changed, e.g onAfterCreate
if (model.getPassword() != null) {
try {
model.setPasswordModified(true);
PortalLDAPExporterUtil.exportToLDAP(model, null);
} catch (Exception e) {
e.printStackTrace();
}
}

For exporting the "userAccountControl" to reflect the user status in AD:
1. Override DefaultPortalToLDAPConverter
2. Add the following in getLDAPUserModifications
addModificationItem("userAccountControl", user.isActive()?"544":"546", modifications);
3. In your UserModelListener, onAfterUpdate
PortalLDAPExporterUtil.exportToLDAP(model, null);
(you can analyse the thread's stack to avoid multiple LDAP export and do it only on actual statusUpdate)

Good luck, and thank you to all those who posted information.

Regards
Hervé

Exporting users' password to LDAP is not working

2009-08-24T05:48:26Z

Hi everybody,

Please have a look to this issue : http://issues.liferay.com/browse/LPS-4608

The problem is that a user's password is not exported to LDAP when he is created. As I performs authentication on LDAP, created users cannot login to Liferay.

In the process of creating a user, either from the Control panel, by self-rgistration or by using the web-services, the UserLocalServiceImpl performs as follows:
- Create the user object in Liferay DB
- Create the contact object in Liferay DB
- The Default ContactListener hook exports the contact to LDAP (I would have expected that the user is exported, not the contact)

I did not find a good way to create a hook to export the user password to LDAP:
- Using a User model hook "onAfterCreate" is not working, as the contact is not exported yet in LDAP when the method gets called : generates an error

In my humble opinion, the password should be exported by the UserLocalServiceImpl.

Liferay's team answer:

Actually when it goes to exportContact, it will(should) export all the user attributes including password. However the variable passwordUnencrypted because that field isn't stored in the database...

So these lines in LDAPUser.java are essentially never run

if (Validator.isNotNull(_user.getPasswordUnencrypted())) {
_attrs.put(
userMappings.getProperty("password"),
_user.getPasswordUnencrypted());
}
[ Show » ]
Amos Fong added a comment - 21/Aug/09 05:34 PM - Visible to - edited Hi Hervé, Actually when it goes to exportContact, it will(should) export all the user attributes including password. However the variable passwordUnencrypted because that field isn't stored in the database... So these lines in LDAPUser.java are essentially never run if (Validator.isNotNull(_user.getPasswordUnencrypted())) { _attrs.put( userMappings.getProperty("password"), _user.getPasswordUnencrypted()); }

My reply:

Thank you for the clarification. I understand and agree the security reason for which the unencrypted password is not stored in the DB. However, as the encrypted is not (should not) exported to LDAP, something is missing.

Moreover, you are mentioning the Contact object. Password is a User attribute, and it is exported to LDAP by the UserListener hook. In hooks, at l east when I create mine, the unencrypted password is not null.

It looks like there is a kind of confusion between Contact and Contact in the design and in the Contact/User lifecyle, is not there?

From a design point of view, I would suggest to separate the User and Contact export process:
- User object should be exported to the security user directory (identification, authentication, and why not externalized authorizations). It is the minima requirement to sign in to Liferay
- Contact object should be exported to a user directory, which could be the internal DB, the LDAP is used as such (common usage of Domino Address Book), or even more valuable to any repository, such as a CRM system (which is my current challenge)

Finally, the user lifecycle is not handled at 100%: when a user is deleted from Liferay, it is not deleted from LDAP. Thus is imported again automatically....

RE: What is use of Catrgoties option in web content in 5.2 version

2009-03-25T08:28:06Z

Hello,

Everyone is expecting a lot from tags and categories. I do either!

I found out:
- Categories and tags and considered as "tag" objects
- Not all assets support categorization. Journal content does, doc lib do not for example
- 2 public render parameters are defined in the Liferay portlet deployment descriptor: "tag" and "folksonomy". The first displays the current selected tag (monovalued), the second is a boolean (false when tag is a category, true when is it a tag)
- Asset publisher is supporting tags defined in 1/ the portlet configuration 2/in the browser URL 3/provided by the public render parameter
- Asset publisher does not combine tags when they are provided by the differents sources (portet, url or param)
- Asset publisher has an unused "categories" object (always empty)

I deployed "Category navigation", "Tag navigation" and "Asset publisher" in one page. I also deployed a small portlet that displays the 2 public render parameters.

By clicking a tag or a category in the navigation portlets, the asset publisher is updated accordingly, and my portlet displays the current selected tag. This works very well.

BUT:
- An asset MUST use the TAGS not categories, because asset publisher is searching assets on TAGS only, not on their category.

Conclusion:
- Categories can be used, but do ont provide less value than tag sets.
- I deleted all my vategories, and I am now using tag sets instead

What would be nice:
- Make a more extensive use of categories in the future to enable dynamic content generation (complete catagory support into asset publisher)
- Add tag/category support to portal pages (without using the /tags/cxxxx in their friendly name...)
- Align the announcement, the content display and the content list portlets to support these nice features

Best regards
Hervé

RE: Web Content Search doesnt work in Liferay 5.2.1 7Cogs example website

2009-03-23T16:32:03Z

Hi Thomas,

Have you resolved your problem?

Web Content search is not working very well on my 5.2.2 server. It returns results, sometimes, when the key word is repeated often.

Best regards
Hervé

RE: Deploying a theme manually- NOT HOT deployment

2009-03-10T17:45:21Z

Hi,

Thanks for the idea. It is actually what I am doing: but the generated WAR gets exploded into the webapps folder. PerhapsI can tune this with the properties.

I was wondering if there were an ANT task I could invoke instead to automate the process.

Nevertheless, I managed to deploy the theme in webpshere by updating the whole EAR, which contains Liferay and the theme.
It appears as a theme, but it is not working: when I select it, a blank page is displayed in the browser, and no log at all.....
Of course it works on Tomcat.

I will continue to investigate tomorrow...

Regards
Hervé

RE: LifeRay 5.2.1, Websphere 6.1 and Custom Themes

2009-03-10T15:38:52Z

Hello,

Have you successfully deployed a Liferay 5.2.2 theme on WAS 6.1 ?

I deployed an EAR, which contains:
- Liferay 5.2.2, context root "/portal"
- my-theme, context root equals to display name "my-theme"

Liferay is working very well, but I cannot see my theme in the theme plugin section.
How does Liferay registers deployed themes when these are not deployed through Liferay UI?

Thank you for your help
Hervé

Deploying a theme manually- NOT HOT deployment

2009-03-10T15:21:32Z

Hello,

I am looking for a way to deploy a customer theme manually, i.e. without using the hot deploy mechanism, which is actually not working on my Websphere environment.

I am using Liferay Plugin SDK to create the new theme.
When I deploy it using the ANT task, the generated WAR is not fully ready for deployment: the web.xml file is missing for example.
The missing files are generated only when the theme is deployed in the application server (e.g. Tomcat) and hot-deployed by Liferay, which one generates a new WAR with all files....

This behavoiur is not working in WebSphere, and I do not want to hot deploy the plugins.

How can I generate the final WAR which contains all the files.

So, what I am looking for is a way to deploy the theme WAR file will all the descriptor files from the Plugin SDK. This WAR file shall be ready for deployment on the application server.

Thank you for your help

Regards
Hervé

Liferay 5.2.2 on Websphere 6.1

2009-03-09T12:13:35Z

Hello,

I successfully deployed Liferay 5.2.2 on WAS 6.1, thanks to the instructions below:
http://www.liferay.com/web/guest/community/forums/-/message_boards/message/2241347

However, I have a serious problem: I cannot stop/start the application, I need to stop/start the server...
See http://issues.liferay.com/browse/LPS-2369

I installed the Liferay with dependencies package. Thus I do not need to configure liferay dependency libs with WAS shared libraries. I moved/copied JARs as instructed.

Have you encountered this problem? Is your Liferay 5.2.2 install on WAS working smoothly?

Best regards
Hervé

RE: [HOWTO] Liferay on Websphere

2009-03-06T14:19:04Z

Hi,

Thank you, your instructions work well. I successfully installed Liferay5.2.2 on WAS 6.1

Regards
Hervé

JSR286 portlets in LEP 5.2.1?

2009-02-09T13:34:32Z

Hello,

I have developed several JSR286 portlets end successfully deployed them on LEP 5.1.2
I have installed lEP 5.2.1 and deployed my portlets: they are deployed and running, and I can add them to a page.
But they are not executed, I mean: the render method is most likely not called.
I can access the other modes, when supported, by again, nothing is displayed in the portlet window.

Any idea?
Thanks

Hervé

Migration from LEP 5.1 to 5.2.1 - Oracle 10g Express

2009-02-09T08:55:20Z

Hello,
I finally managed to migrate from Liferay 5.1.2 to Liferay 5.2.1.
My existing site was containing some stuff I did not want to lose when upgrading to 5.2.1, and I am not interested in the default data loaded by Liferay 5.2.1.
Environment:
- Oracle 10g Express
- Liferay-tomcat-5.5-5.2.1
Preparation:
- Backup your database
- Unzip the liferay tomcat bundle : I used a new directory to not override the existing version,but I will have to redeploy all my themes, portlets, and customizations.
DB configuration (if you do not use your application server's JNDI datasource):
- Create the portal-ext.properties file
- Add the following lines:

1jdbc.default.driverClassName=oracle.jdbc.driver.OracleDriver
2jdbc.default.url=jdbc:oracle:thin:@localhost:1521:xe
3jdbc.default.username=your_user
4jdbc.default.password=your_password

- Add the following properties:

1schema.run.enabled=false
2schema.run.minimal=true

- Copy the Oracle driver JAR file to <tomcat_install_dir>/common/lib/ext
- Delete the "sevencogs" theme and hook from the tomcat's "webapps" folder
- Edit the "webapps/wol-portlet/WEB-INF/jdbc.properties"
- Configure the DB :

1jira.driverClassName=oracle.jdbc.driver.OracleDriver
2jira.url=jdbc:oracle:thin:@localhost:1521:xe
3jira.username=your_user
4jira.password=your_password

- Delete the "data/hsql" directory if exists (if it is created again, then something is wrong in the configuration)
Now start Liferay: in the logs, the Dialect detector should find Oracle. The auto-upgrade process will upgrade your database. When the WOL portlet is initialized, Oracle should be detected as well.
Finally I deployed all my custom assets (themes, portlets, ...)
Hope this helps, and comments are welcome ;-)
Regards
Hervé

RE: LEP 5.1.2 - Flash & WMV : Journal + Document library : IE

2009-02-03T13:09:59Z

Hi Angelo,

Unfortunately, I have never succeeded in displaying FLV movies.
My patch supports only WMV and SWF files. I tried on FF, IE & Chrome.

sorry...

Regards
Hervé

RE: LEP 5.1.2 - Flash & WMV : Journal + Document library : IE

2009-01-27T06:58:35Z

Hi Mohammed,

I guess the patch is available (yet) in trunk, I actually do not know...
You should compare my fix vs. trunk

Regards
Hervé

RE: Journal draft articles

2009-01-27T06:52:44Z

Hi Rohan,

Mmm... Let's step into all details, I may have forgotten something.

I have created a community called "Marketing".
I have created a community role name "Marketing"
I have created a community role name "Direction"

I defined the following portlet permissions for the role "Marketing":

Portlet - Resource - Action
Journal - (no resource) - Add Article
Journal - (no resource) - View
Journal - "Journal Article" - Delete
Journal - "Journal Article" - Expire
Journal - "Journal Article" - Permissions
Journal - "Journal Article" - Update
Journal - "Journal Article" - View

Why cannot we create tables in the forums?! Why not the same editor as in Journal??? :-(

I defined the following portlet permissions for the role "Direction":

Portlet - Resource - Action
Journal - (no resource) - Approve Article
Journal - (no resource) - View
Journal - "Journal Article" - Expire
Journal - "Journal Article" - View

I assigned a user to the community "Marketing":
1. Assign the user "MakertingUser" as community member
2. Assign him to community roles ([assign user roles] link)
3. Check "Marketing"
This user is now assigned to "Community member" and "Marketing" roles in the Marketing community

I assigned a user to the community "Direction":
1. Assign the user "DirectionUser"
2. Assign him to community roles ([assign user roles] link)
3. Check "Direction"
This user is now assigned to "Community member" and "Direction" roles in the Marketing community

Connect with "MarketingUser" and navigate in the Marketing community "Journal" page: your user is allowed to add articles, to submit it for approval, but not to approve it.

Create the article, and submit it for approval. If emails settings are correct, you should receive a notification email. It is not required to proceed further.

Now connect with "DirectionUser" and navigate in the Marketing community "Journal" page: search for non approved articles, you will see the one you created. As you can see, the user cannot edit it, but preview it only.
Preview the article: the "Approve" action is available (in the workflow section).
Approve it, and you're done!

If your installation does not behave as expected, please check the following:
- I am running LEP 5.1.2
- I deployed the fix, which is available for download in my first post

Regards
Hervé

RE: LEP 5.1.2 - Flash & WMV : Journal + Document library : IE

2009-01-27T06:15:23Z

Hello,

Apparently, Liferay will be fixed in 5.2.1, see: http://issues.liferay.com/browse/LPS-1004

Regards
Hervé

RE: Journal draft articles

2009-01-23T14:25:00Z

Hi Rohan,

Thank you for testing ! Always appreciated :-)

Have you read the fix description I published in JIRA? http://issues.liferay.com/browse/LPS-856
It is actually more detailed than in the forum.

What I did not like with the original version of Journal, is that as soon as you perform the "Save" or "Save and continue" action, the email is sent to request the approval.
So I removed the automatic email notification on these actions: the article is saved, as draft, as no approval request is sent.
However, the "draft" status does not exist (draft = saved + not approved)
To send the email for approval, I added the "Request approval" action. It simply sends the email.

(Do not care about messages in the console, it is an simple way to check whether my classes are used in place of Liferay ones)

Regarding permissions: you can create roles in Liferay Enterprise Admin.
- I created the community role "Marketing" (Marketing can add and update content in CMS), and defined permissions. See attachment. Users assigned to this role will not be able to "approve" an article.
- Then I created the community role "Direction" (Direction can approve articles), and defined permissions. See attachment. these users can only approve articles.

Finally assign your users to their respective role.

"Request for approval" can be improved by setting the requester's email address instead of the address configured in the portlet. Gloria is working on that I think.

Regards
Hervé

RE: Journal draft articles

2009-01-23T09:51:30Z

Hi Gloria,

I have not been using the ext environment, thus I cannot help you much... I think it is well explained on Liferay wikipedia.
In the ZIP bundle, I packaged the complete stuff, but you need only the files I modified in your ext environment. Have a look the their timestamp.

Regards
Hervé

RE: [RESOLVED]: SOAP calls from PHP app + nuSOAP : data types

2009-01-19T15:16:41Z

In my example, you do not need SSO to view the information as soon as it is "public".
But if you want to post a message (or to perform any action which requires authenticaion), either you authenticate in the ifram (not very nice though it works), or you implement SSO for a nice integration in your web app.
I do not say it is required.

Regards
Hervé

RE: [RESOLVED]: SOAP calls from PHP app + nuSOAP : data types

2009-01-19T13:59:14Z

Hi,

You should find all the information you need about CAS in the forums and in the wiki (http://wiki.liferay.com/index.php/Main_Page). And of course on their official web site (http://www.ja-sig.org/products/cas/)

To your second question: create a page in Liferay, and set a friendly URL (You can do that in "Manage pages").
In this page, add your portlet.
Your URL should be similar to this one: https://www.liferay.com/web/guest/community/forums
Without the friendly name, it would be: https://www.liferay.com/web/guest/community/11
Where '11' is the page ID...

As you can see, the message board portlet is displayed. Just imagine you configure your page with a blank theme and no border, and the integration into an Iframe should be ok.

Simply write this code in any HTML file, and you will see the result.

1<html>
2<head><title>Demo Iframe - portlet</title></head>
3<body>
4<h1>Below is the iframe</h1>
5<iframe scrolling="auto" frameborder="0" width="100%" height="800" src="https://www.liferay.com/web/guest/community/forums">
6<h2>Your broser does not support IFRAMEs</h2>
7</iframe>
8</body>
9</html>

Regards
Hervé

RE: [RESOLVED]: SOAP calls from PHP app + nuSOAP : data types

2009-01-19T06:35:11Z

Hi,

Interesting question! I do not have any answer...
The simplest solution would be:
- Deploy the Liferay portlet in a Liferay page, with a "blank" theme (no decoration) and the 1-column page layout. Remove the borders.
- Configure a friendly name
- Use an Iframe in your web application with correct attributes to make a seamless integration.
- If needed, implement a SSO solution: CAS or Tomcat mechanisms can do the job. Make sure the users are identified under the same identity in both apps (access control), or use impersonation if sufficient.

Regards
Hervé