I use sssd. I normally edit /etc/sssd/sssd.conf in order to configure the
package. In Leap 15.6 such file does not exist. I found in the packages sssd
the file /usr/lib64/sssd/conf/sssd.conf and, for testing, I made my changes
there.
When I started sssd.service it didn't start. The presence of
/etc/sssd/sssd.conf is required for the service to run although I didn't find
any reference in /usr/share/doc/packages/sssd to the fact that the user is now
required to create /etc/sssd/sssd.conf from scratch.
I then made a copy of /usr/lib64/sssd/conf/sssd.conf to /etc/sssd/sssd.conf and
changed it. When I started sssd.service it didn't start. The file
/etc/sssd/sssd.conf can be readable only by root, but the file
/usr/lib64/sssd/conf/sssd.conf did not have such permission and when I made the
copy, /etc/sssd/sssd.conf was world readable as well. After changing the
permission of /etc/sssd/sssd.conf I was finally able to start sssd.service.

Please does not make such disruptive changes without giving the user indication
about what it is required to do (that was not required before) before the
program can be used.
I suggest to put back /etc/sssd/sssd.conf with proper permission containing
only commented lines explaining what and why the changes were made and what the
user is supposed to do now.
In this way may be other users will not go through the painful trial and error
process as I did, before being able to use sssd in Leap 15.6.