Thanks Riccardo. I have tried using hooks and ext plugin. Hooks seems to work for my purpose, however I am stuck now with the following:
a) Since we have custom authenticator, the User information will not be stored within liferay. It will be handled by us. Unfortunately, liferay requires the user to be in its database as it is used somewhere. Similar to this one
b) I did try to create a dummy liferay user. when our user logs-in to the application, we will assign the dummy userID to it to keep liferay happy. Unfortunately during redirect to the default landing page, the user will be null (from hours of debugging), hence liferay says the request failed to complete. We did verify that we have logged in correctly to our own service. it is when returning to liferays control that liferay complains the request is not completed.
c) during debug, we found that ifwe replace the static login page portal/c/login with our own landing page, the complaints stop and liferay is happy. Where could i possibly replace the default login/logout page? (ive tried liferay-hook and portal-ext.properties) and failed to make it work.
