After upgrade to 3.1.4 we've run into problems when creating new
protected resources; when new protected resources are configured to use
Web Server Host Name instead of Forward Received Host Name, they still
use the latter. Old configurations work fine.

Very weird, this should be and has been very easy to use. We just can't
figure it out. Another thing is that even if we configure path to a
certain login page, NAM adds forward slash (/) after the url (like
login.asp/ when it should just be login.asp).

Has anyone faced a similar situation? Any help would be highly

vesapi's Profile:
View this thread: