Hey, everybody. Can you tell me what I'm doing wrong? On the server created a base domcfg.nsf, configured forms with errors, but, when trying to open the base to which there is no access comes out the standard error 401. Customized error does not appear. What is wrong?
Hello Moises,
You can also refer the article on "How to show a customized message when accessing an unauthorized database on the Domino web server using the domcfg.nsf login form"
Reference Document : https://support.hcl-software.com/csm?id=kb_article&sysparm_article=KB0088880
Hi @Moises Romero Barraneche
Verify if Domino server is configured with session based authentication?
Tried restarting HTTP task after setting up mapping in domcfg.nsf?
Is it working correctly for other errors or is the issue specific to authorization failures. Also try creating a web site document with session authentication option if not done already. Restart the domino server after making the changes.
Hi moises Just a thought, although i havent encountered multi server authentication scenario.
Is the relevant domcfg available on the server on which you are getting an error?
Is the matching error form mapping required to be configured on every server being accessed?
Domcfg is on all servers and is a replica. All forms are on all servers. But it doesn't work. I've already racked my brain. Maybe it's a bug?
Hi moises
I tested with single server session auth as well as saml auth. Auth failure does not fire the relevant error form. All other cases it works. Most likely a bug unless we are missing some additional setting.
However in above two cases it offers the login form and not 401
Try going with the following scenario.
Log in as a user and try to open any database that the user does not have access to, such as log.nsf. What form will you see?
I have tested exactly as you say. The moment i try to open a db to which i dont have access, i get the login form. I tried with log.nsf as well as some xpages applications. The error forms of domcfg fire correctly on all other errors. But i havent been able to test on your scenario ie multiple servers SSO. If it works for all other errors except this one, it is definitely a bug. I couldnt find any thing else you are supposed to do more than what you have already done.
