Skip to content

Streamline authentication process#5387

Open
nilmerg wants to merge 5 commits intomainfrom
streamline-authentication-process
Open

Streamline authentication process#5387
nilmerg wants to merge 5 commits intomainfrom
streamline-authentication-process

Conversation

@nilmerg
Copy link
Member

@nilmerg nilmerg commented Jul 8, 2025

Please see commit descriptions

@nilmerg nilmerg added this to the 2.13 milestone Jul 8, 2025
@nilmerg nilmerg self-assigned this Jul 8, 2025
@nilmerg nilmerg added area/framework Affects third party integration/development area/authentication Affects user authentication or authorization affects-upgrades The change requires migration or user awareness labels Jul 8, 2025
@cla-bot cla-bot bot added the cla/signed label Jul 8, 2025
@nilmerg nilmerg force-pushed the streamline-authentication-process branch 2 times, most recently from 02f3532 to e21071c Compare July 8, 2025 14:41
@nilmerg nilmerg force-pushed the streamline-authentication-process branch 3 times, most recently from 2a857f1 to 4534aad Compare February 11, 2026 11:48
nilmerg added 5 commits March 11, 2026 17:14
It is nowadays no exception that stylesheet may be dependent
on who's using the app. So to avoid race conditions like
in #5385 authentication is an explicit step during bootstrap
now.

fixes #5385
Since authentication is now performed even for static
resources, there's no reason anymore to support implicit
authentication. This also limits authentication attempts
to a single one, previously failed attempts were repeated.

Requiring authentication during bootstrapping, i.e. before
authentication has been performed, will now throw an error.

refs #5265
So that authentication can suspend it. There are cases,
e.g. cube, where authentication is required in run.php.
During bootstrapping loading modules is mostly required
to load libraries, register routes and hooks. Most of the
time authentication is not required for these, but if
it is, evaluation is now interrupted and continued
after authentication has actually been performed.

I don't see a real risk for any breaking change here,
since authentication happens shortly after. It actually
avoids a breaking change, since without this, cube's
Icinga DB support would break or at least malfunction.

And cube is only a single example.

refs #5265
The related controller action is gone since
b6b5caa
Providing a user or user group backend in configuration.php
now triggers a deprecation or warning. They are expected to
be announced in run.php, just like hooks. Authentication
attempts during a configuration.php run, while Authentication
has not been performed yet, will be also suspended now.
This ensures that the current behavior, being broken or
working, stays the same.

refs #5265
@nilmerg nilmerg force-pushed the streamline-authentication-process branch from 4534aad to 36314e1 Compare March 11, 2026 16:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

affects-upgrades The change requires migration or user awareness area/authentication Affects user authentication or authorization area/framework Affects third party integration/development cla/signed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

CustomUserBackend is loaded too late Users who are not allowed to change the theme, cannot change the theme mode either

1 participant