skip to main |
skip to sidebar
One of my colleague was engaged in an assignment this week where he needed to revert back the existing security with LDAP to out-of-the-box security (File repository). Here are the steps which we followed to complete this task.
We are using portal 6.1. So, we need to install the required patch for this task. We installed PK73815 and update the Portal configuration. You can down load this APAR from the IBM fix central.
- Modify the wkplc.properties file for the following changes. Add this properties at the end fo the file.
# The realm name to be used. A realm with this name will be created.
restore.file.realm=federatedRealm
restore.file.delimiter=/
# Portal and WAS admin UID (short name) and password
restore.file.primaryAdminId=adminUID
restore.file.primaryAdminPassword=adminPWD
# CN of portal admin group (short name)
restore.file.primaryPortalAdminGroup=adminGroupCN
- Make sure that your WAS admin password and your Portal admin password are populated in wkplc.properties file.
- Start Websphere Application Server and Websphere Portal server before running the task.
- Navigate to the /opt/ibm/WebSphere/wp_profile/ConfigEngin directory. Run the following command from here.
wp-restore-default-repository-configuration - The wp-restore-default-repository-configuration task allows you to return to the default VMM setup with a federated file repository. The task will create a new realm, delete all existing repositories, and configure a file repository in VMM.
- If you want the admin user to be added to the admin group, restart both the servers and run the following command from /opt/ibm/WebSphere/wp_profile/ConfigEngin
wp-restore-default-repository-add-group-member
This process will revert back your repository back to out-of-the-box security.
References:
http://www-01.ibm.com/support/docview.wss?rs=688&ca=portall2&uid=swg21368395
It's sometimes so frustrating to see that some thing which you have already done once is giving you a hard time doing again.
This is exactly what I faced today. I have configured anonymous access to the web content for my site and have configured Web Content Viewer portlet for anonymous access in my devl environment. But when I tried the same thing today in Production, it's just not working. After so many tries looking for the solution what I found, is a small mistake which cost me dearly.
This has again inspired me to put this thing on papaer to make my life easy. So, for all you people out there who are also into such kind of scenarios, here is a quick note on how to assign anonymous access to web content.
Steps:
- Create a copy of the "Web Content Viewer" portlet and rename it to whatever name you like.
- Add "Anonymous Portal User" into the user role of the portlet.
- Add "Anonymous Portal User" into the user role of your content library.
- If point -3 doesn't suits to your access policy, then atleast make sure that you need to have user access for "Anonymous Portal User" on every item in the path to the current content item. i.e. library/site/site area/content item and ofcourse on the Authoring Template and presentation Template.
- Modify the Edit Shared Settings in the portlet and configure the content item to be displayed.
Hope this helps to some extent when you really need it. :)
It's been quite a while since I blog . Busy with ongoing assignments and of course my wedding is around the corner. :)
For the people who are more aligned towards portal administration rather than development, here is collection of all the details/know-how which will be handy while working. This is a one stop shop for administrator.
http://www-10.lotus.com/ldd/portalwiki.nsf/dx/learning_portal_for_administrators
