Messages

The file /boot/loader.conf.local doesn't exist. I actually enabled the delay in the file located at /boot/defaults/loader.conf

Then why am I running into issues where old password and still working after a change in LDAP. and its not just the old password, I am able to use the users new AND old password to login.

May I also ass that ad administrative (added to admin group in GUI and given all rights) still cannot make a number of changes, for example when I tried to delete a static route, I didn't get an error but it wasn't deleted but it works fine as root. Same with any changes made in the system access section, no error but no change.

I just finished setting up LDAP which so far is flaky at best. The first major thing I notice is that it is fully manual. although it binds to users, I still have to manually add each user rather than it monitoring or checking a user against a security group membership for permissions.

The second thing I notice that is a major concern is that all the information it uses seems to be cached. I am able to import a user and login, but if I disable the user in AD afterwards, they can still login without issues. I changed the password for one of these users and was able to login using the new password as well as the old interchangeably, another major security concern.

Is there a way to clean this functionality up or should I just disable all LDAP based access on the system?

I did end up enabling a delay in the loader.config file which appears to have fixed it

Hello,

Im trying to resolve an issue with a new installation, I was able to get everything installed and setup without issue EXCEPT:

I'm using a three NIC setup to have an out of band management port which I was able to configure and have work exactly as expected, but as soon as I reboot I see the message during boot that says "Default interfaces not found -- Running interface assignment option." which is totally automated and reset all my interface config and breaks my setup.

Is this a self-healing option I can simply disable or is this a software bug of some sort?