so let’s take a step back and look at this problem, we are after all web developers right?
what’s going here is the cookies aren’t sticking, that’s why the request after login works and the next request is prompting a login.
so how do we debug this problem? now that i have set out the problem, let’s diagnose
firstly as other have suggested, try in incognito/private mode, that means each round of testing, close and reopen the private/incognito browser window.
look at the response in dev tools from the login, there will be a set-cookie header
5.4.3 sets path scoped cookies for the admin, i.e path=/lucee/admin (latest version 5.4.3.8 also works for rewritten / remapped admin paths like /blah/lucee/admin)
the next request should then be passing the cookies from the set-cookie header to the next request, if they aren’t passed, that’s the problem
also check the browser console for cookie warnings and the dev tools panel to see what cookies are set
try this is both FF and Chrome
do all this with the latest 5.4.3.8-SNAPSHOT, that should always be one of the first steps in debugging a problem with Lucee, try the latest SNAPSHOT as you might be simply battling already solved tech debt