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
LDAP can currently be used to provide access to a CDash instance, but it cannot provide per-project authorization. As CDash moves towards a GitHub- or GitLab-style structure, having the ability to control project access based on LDAP groups is a very useful feature.
The text was updated successfully, but these errors were encountered:
NOTE: This PR moves cleanup logic out of the request-triggered daily
update script. To continue having these cleanup tasks performed
automatically, administrators of non-Docker systems must run `php
artisan schedule:run` via cron or similar.
The current "daily update" process is clunky, and in dire need of a
refactor. This PR takes the first step towards modernizing the daily
update process by separating out a few small portions of the process
into independent "tasks" managed by Laravel. This PR also develops the
infrastructure needed to eventually perform LDAP syncing for
#1983.
Laravel overhauled the task system in Laravel 11, but we can't upgrade
to Laravel 11 until Red Hat releases a UBI image with PHP 8.2+.
Feature Request
How can we make CDash better?
LDAP can currently be used to provide access to a CDash instance, but it cannot provide per-project authorization. As CDash moves towards a GitHub- or GitLab-style structure, having the ability to control project access based on LDAP groups is a very useful feature.
The text was updated successfully, but these errors were encountered: