Hi Matt!

We have only one customer using custom AGW logout pages. They are currently running AM 5.0.2.1.

I've checked what we have done there and we customized logoutSuccess.jsp. Please note that this customization happened years ago (I think still in 3.x version) so it might be that this should now be done somewhere else.

Looking at vanilla AM 5.x logoutSuccess.jsp I see following:

So either logoutSuccess_legacy.jsp or logoutSuccess_latest.jsp is called. Change in those two files should be somehow seen...

Kind regards,

Sebastijan

So yeah, in earlier versions, you could just modify logoutSuccess.jsp and be done.  But starting somewhere around 4.5 I think they changed this to have "legacy" and "latest."  I've honestly never fully understood this confusing setup, but the NAM documentation says for a custom AG logout page, modify logoutSuccess_legacy.jsp and doesn't explain much more.  As far as I can tell, nothing ever loads, uses, or reads logoutSuccess_legacy.jsp (at least I cannot find it).  I was hoping someone would explain to me what I'm missing there.

Anyway, what I found is that the nidp_latest.jsp loads logoutSuccess.jsp which in turn loads logoutSuccess_latest.jsp content, at least by default (and there is an nidp_legacy.jsp as well, not sure what reads that).  Contrary to what I said in the original post, I am seeing my modified logoutSuccess_latest.jsp content on logout, that is working.  I'm just hesitant to start messing with these JSP files, especially since the documentation makes no mention of modifying them.  I could change stuff in nidp_latest.jsp or in logoutSuccess_latest.jsp to effect what I need.  But I want to do it the RIGHT and SUPPORTED way and I cannot tell what that is.

Matt

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.

alexander_miltenburg said:

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

Hey there, I'm currently facing some challenges with implementing a custom logout page on the ESP (Enterprise Service Portal). According to the documentation, I should modify the logoutSuccess_legacy.jsp file. However, it appears that this page is not being called during the logout process, and any changes I make to it are not visible. It seems that the logout process is primarily handled by nidp_latest.jsp. I also attempted modifying logoutSuccess_latest.jsp, but the content I added there doesn't seem to be displayed either. I'm using NAM 5.0.2.1.

By default, the content from logoutSuccess_latest.jsp should be displayed on logout against the AG.  I just looked and the last time I had to modify the logout page it looks like I did it there.  I'd try something real simple first, like just adding some text, and see if that appears.

Matt