Another OSU problem: .PROTECT

[Willem Grooters]

I have installed and configured the OSU webserver - logically 100% copy of an older machine in configuration, just a few changes required:
* System authorisation files do not reside on the system disk, for we need to test different VMS versions and this allows us to do so with minimal extra work.
* There is not just OSU, but SWS (and in future, WASD) as well, because we need to check functionality between the webservers. Of course, all aff the system disk.
* The application files (.HTML, .COM and all related) are in one directory that is aliassed (SET FILE/ENTER) into the webserver roots, to have a situaltion that is similar to production.
* This allows us to have webserver confurationfiles equal between the old and new system, where it concerns the web application.

The root of the webaplication is protected by LEVEL2.PROT on both systems, and since the application and it's accesors will be the same, and theer is no chnage in prtection scheme between the two systems, I copied both .PROT files. However, I could not login into the aplication - as I found out, I needed to build cel-auhenticator on the new machien since it wasn't build in the base syetem.

So now it is, but still, when .protect on these locations is in effect, NO ANY username/password is accepted and all acess to the application is denied. The very same configuration on the old machine - including protection scheme, works.

Could this be casued by the fact that the actual SYSUAF is off the system disk? (logical SYSUAF is properly defined (/SYSTEM/EXEC)), or is the fact the root of the application is just an alias?

[David Jones_21 · Accepted solution]

The authenticator image must be installed with privileges, one of the tasks normally done by HTTP_STARTUP.COM. Look at the server's error/trace log to determine if the authenticator is running with SYSPRIV. .prot files used with cel_authenticator should be compatible with the ext_authenticator that replaced it.

The authenticators use the supported $GETUAI API to read SYSUAF and have not problem with it located off the system disk.

[Willem Grooters]

Is isn't! Nor has HTTP_STARTUP.COM done it. And I found why ;-), but still one question:
HTTP_SYSTARTUP.COM specifies image "ext_autheticator.exe" to be installed and and "ext_autenticator" as a logical. Should both "ext" be replaced by "cel" and what would the logical nee to point to?

(Sorry about my ignorance but I'm new to OSU and need to have it installed in a too short period)

[Willem Grooters]

Never mind.
It works fine with ext_authetication (should have read better)