Check carefully. Note -- in ^%ISCLOG (with percent) you enable the log. Then you read ^ISCLOG (without percent) in %SYS namespace.
When I repeated steps that I suggested to you, I saw the following error in ^ISCLOG

/* ERROR #5002: ObjectScript error: <PROTECT>^%CSP.Login.1 ^|^^c:\intersystems\iris2023x1\mgr\|dc.CustomLogin.1 */

Then I enabled auditing of Protect events, reproduced the eror and got more details:

Description:  Attempt to access a protected resource
Timestamp:    2023-03-19 16:01:38.000   Username:     CSPSystem
UTCTimestamp: 2023-03-19 15:01:38.000   Pid:          10896
Event Source: %System                   JobId/JobNum: 131089/17
Event Type:   %Security                 Session ID:   eK95W6SMCS
Event:        Protect                   IPAddress:    127.0.0.1
System ID:    DEP5570AKOBLOV:IRIS2023X1 Executable:   CSPa24.dll
Namespace:    %SYS                      Index:        196
Roles:
User Info:                              O/S User:     CSP Gateway
Routine:      ^%CSP.Login.1 |"^^c:\intersystems\iris2023x1\mgr\irislib\"|
Authentication: Password
Event Data:
<PROTECT>^%CSP.Login.1 *^|^^c:\intersystems\iris2023x1\mgr\|dc.CustomLogin.1

Indeed, user CSPSystem does not have READ permission on irissys database, where custom login class is located. Rather I should have created a new role that has only READ permission on %DB_IRISSYS resource, not RW.

I added role %DB_IRISSYS to user CSPSystem, closed connections from Apache to IRIS, so that the role is added on new connection, then login page began to work

Documentation has an important note about this parameter:

This parameter has been retained for compatibility, but should not be used when building new applications.

https://docs.intersystems.com/iris20223/csp/docbook/Doc.View.cls?KEY=RAC...

Yuri, enable ISCLOG, reproduce the error, disable ISCLOG and then check if it has any errors, e.g. errors.

%SYS>kill ^%ISCLOG, ^ISCLOG
%SYS>set ^%ISCLOG = 3
//reproduce the error
%SYS>set ^%ISCLOG = 0
%SYS>zw ^ISCLOG

Afaik, with custom login pages user CSPSystem needs to have READ permissions on a database where custom login page class is located

In HealthShare section you see Extended Maintenance kits
In Continuous Delivery section you'll find Health Connect 2022.3, 2022.2

404 is also returned when there are some permissions issues.
Try to give %All to the user that you calling this API with and see if it helps. If yes -- then this is permissions issue.
Or enable Audit and auditing for Protect event and see if it is logged in Audit when the problem happens

Other idea -- enable ISCLOG, reproduce the problem, disable ISCLOG and see if there are any errors there. ISCLOG is very verbose, so just do one HTTP request with ISCLOG enabled

enable:

%SYS>kill ^ISCLOG,^%ISCLOG
%SYS>set ^%ISCLOG = 3

disable:

%SYS>set ^%ISCLOG = 0

analyze:

%SYS>zw ^ISCLOG (yes, without %)

Generally, you should install external web server and use it with the application. Private Web Server (the one that runs on 57772) are for Management Portal and some basic tests only

https://docs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY...

Choose Logical Mode in dropdown near the Query Builder. Perhaps IRIS SQL tries to do some Logical -> Display conversion and fails.

See also

SET OPTION PKEY_IS_IDKEY = true

With this enabled your sample works as you expect

https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls...

Mark, you need to close connections from Web Gateway to IRIS, so that Web Gateway reconnects and CSPSystem logins with the new role. You can do this in Web Gateway -> Status page -- close button for the second table. Or just restart the web server.

Note -- Roles field in the Audit details. Check that it has %DB_SRFT role when happens again.

In System Explorer -> Globals check "Show SQL Table Names". You'll see information on how particular global is used.