This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Custom Logout Page

Can someone explain how you use a custom logout page on the ESP?  The documentation says to modify logoutSuccess_legacy.jsp, but as far as I can tell, nothing ever calls that page and any content I put in there is never seen on logout.  It seems like logout is solely built form nidp_latest.jsp.  I tried modifying logoutSuccess_latest.jsp as well, but I don't see that content either.  This is NAM 5.0.2.1.

Thanks.

Matt

Parents Reply Children
  • 0   in reply to 

    This describes modifying the logout page, so that is supported by CR/MF/NetIQ:

    https://www.microfocus.com/documentation/access-manager/5.0/admin/bixm0pw.html

    And here https://www.microfocus.com/documentation/access-manager/5.0/admin/get_start_idp_custom.html you can read: "If the /opt/novell/nids/lib/webapp/WEB-INF/legacy folder exists, then the active user interface is the legacy layout"

    One warning from experience modifying the jsp's heavily, creates extra work during upgrades because you have to redo either your own work or the upgrades from NetIQ.

    I'm talking about the logout page on the ESP/AG, not the IdP.  That documentation is here:

    Customizing Access Gateway Logout Page

    And it only talks about modifying logoutSuccess_legacy.jsp, not logoutSuccess_latest.jsp. I don't see any mention of logoutSuccess_latest.jsp there, although that is what you have to modify.  And there is no mention in that section about the legacy structure.  It's completely ignored w/r to the AG.  So following these docs wouldn't result in success.

    I've never liked or used that legacy structure, that was a poor design decision from way back that makes no sense to this day.

    Oh believe me, I recommend strongly against modifying any of the default JSPs. I've been burned in the past by  modifying nidp_latest.jsp only to find it having changed during an upgrade and then I'm stuck re-integrating my changes.  So I get that it's a lot of extra work during an upgrade.  It's a bad design to require customers to be modifying these JSPs like this in order to do customizations.

    What I typically recommend is having a logout "landing" page located elsewhere (e.g. another web server) to handle the logout "logic".  That is a far better approach and then you don't have to mess with the logoutWhatever JSP pages.  Unfortunately, I'm in an upgrade/migration situation where I'm coming from a super old version of NAM to current and I have to maintain existing functionality for the time being, hence I have to modify logoutSuccess_latest.jsp (against my better judgement!).

    Matt