After Web Help Desk Hot Fix - the Save and Cancel buttons are missing

Looks like I stumbled across another bug.  Trying to email a client password reset link, the email goes out, but the link provided ends up getting a 403 error.  

I've isolated this to the new section in the tomcat_server_template.xml file.  Remove it and the reset link works as expected.  Confirmed in multiple systems.

Have you logged with SW Support?

Yes, yesterday.  Case #01748587

james.kluza  Did you ever get a fix from SW support for the broken password reset link problem? We are having this problem now after updating to HF2. Due to all the security issues with not having HF2 installed, we can't downgrade and need to live with the broken password link issue at this point. I put in a ticket myself with SW Support earlier this week and I referenced your ticket number and so far I am still in the stage of them asking me for basic info like log files and they haven't acknowledged anyone else ever having this problem. It looks like the new lines in the tomcat_server_template.xml file need to be in place for a complete fix to the security issues so I don't want to remove them.

It's "with development". Other than that, only thing I've received is the automated "Case Inactive" emails.  Yes, I can't speak to the overall impact of removing the valve statement in the tomcat_server_template, just that it is the cause of the issue.  I'd guess there is something in the expression statements that needs to be modified, but I'm not wasting any more time on developing their solution.  

Thanks! Good to know we are not alone. If I get some kind of solution from SW support before you do I'll let you know.

Just got the same response back from SW support as you did. They acknowledged the issue as bug and "...our development team has prioritized a fix according to the severity and scope of impact." Rest of the response says they put my support ticket into an archived state and that I should keep checking the release notes of future WHD releases to know when the bug has been fixed.

Just got the same response back from SW support as you did. They acknowledged the issue as bug and "...our development team has prioritized a fix according to the severity and scope of impact." Rest of the response says they put my support ticket into an archived state and that I should keep checking the release notes of future WHD releases to know when the bug has been fixed.