You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: LDAP Sync Button Missing for Administrators #19603
It looks like in the latest version, the LDAP Sync button is no longer available for administrators.
It only appears for super admins. Is there a way to give administrators access to this without making them a super admin?
What browsers are you seeing the problem on?
Microsoft Edge
Can you reproduce this on the public demo?
N/A
Do you have full multiple company support enabled?
No
If you have full multiple company support enabled, do you have location scoping to company enabled?
I do not have full multiple company support enabled
Application log output
Browser console output
Common Issues
I have searched this repo for existing issues related to my issue (including closed issues)
My APP_URL is set correctly in my .env file (including http or https and no trailing slash)
I have searched the official Snipe-IT documentation and have checked the Common Issues documentation (where applicable)
I have run database migrations (where applicable).
I have attached screenshots and/or videos of the issue (where applicable)
That's not really a bug, it was a choice we made. LDAP syncs should really be run on a cron, as they can often time out on larger directories, and with FMCS+location scoping, it gets messy letting users who could be company or location-scoped touch things that cross companies/locations.
Ok, understood. With that in mind, could we have a least an option within Snipe to have the LDAP sync run on a fixed schedule?
This would make it easier for container deployments without having to make up shell scripts to hook into the container to run it.
Starting from Snipe-IT v3.0, all automated tasks are handled via the scheduler. To set a cron job to run every minute to ping the scheduler: * * * * * /path/to/php /path/to/artisan schedule:run >> /dev/null 2>&1 The scheduler already knows how often it should trigger the individual tasks, because of…
❗️ Large LDAP Directories: In your .env file, you may need to modify the LDAP_MEM_LIM (expressed as '500M' for 500MB) and/or the LDAP_TIME_LIM (expressed in seconds) in order to avoid a large LDAP sync from timing out or exhausting all memory. The default time limit is 10 minutes. The default memory…
Activity
snipe commentedon Sep 1, 2026
That's not really a bug, it was a choice we made. LDAP syncs should really be run on a cron, as they can often time out on larger directories, and with FMCS+location scoping, it gets messy letting users who could be company or location-scoped touch things that cross companies/locations.
PP-JN-RL commentedon Sep 1, 2026
Ok, understood. With that in mind, could we have a least an option within Snipe to have the LDAP sync run on a fixed schedule?
This would make it easier for container deployments without having to make up shell scripts to hook into the container to run it.
snipe commentedon Sep 1, 2026
You own the container, so you always have that option.
You'd want to set up a cron in the container that periodically runs
php artisan snipeit:ldap-sync