Custom loginhandler prevents usage of atomic planner

Hello,

we implemented a custom loginhandler. It is basically the default loginhandler with the addition, that only specific ldap users are able to log in. The other ones are not allowed to login, not even in "blue-mode" (what would be the default).

However when we activate the custom loginhandler in the local.yaml the atomic planner disappears and all other planners stop working. When we change it back to the default loginhandler, everything works as normal again.

The question now is, how are these two things connected? We are relatively sure, that there isnt a bug in the custom loginhandler, as its basically just the default handler copy pasted with a small addition.

Does anyone maybe have an assumption, how these two components might be connected?

Start with the custom and default loginhandler implementations and the loginhandler setting in local.yaml. Reproduce the issue with the atomic planner enabled, then trace how authentication affects planner availability and execution. Done means identifying the connection and restoring the atomic and other planners when the custom handler is enabled.

Written by the indexing model from the issue text.