matomo-org / matomo-org/plugin-LoginLdap
Configuration failed "LDAP access synchronization not enabled. "
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 37
- Forks
- 30
- Avg merge
- 22h 53m
- Merged PRs (30d)
- 19
Description
The configuration for LDAP plugin is failing.
After enabling the logging (log type debug), I found below messages:
DEBUG
LoginLdap
2015-11-05 02:49:48
1f7a8
Auth\Base::tryFallbackAuth: normal auth returned result code 42 for user ''
DEBUG
LoginLdap
2015-11-05 02:49:48
1f7a8
Auth\Base::tryFallbackAuth: trying normal auth with token auth
DEBUG
LoginLdap
2015-11-05 02:49:48
1f7a8
authenticateByPassword: empty login encountered
DEBUG
LoginLdap
2015-11-05 02:49:48
1f7a8
Auth\Base::tryFallbackAuth: normal auth returned result code 0 for user ''
DEBUG
LoginLdap
2015-11-05 02:49:48
1f7a8
Auth\Base::tryFallbackAuth: trying normal auth with token auth
DEBUG
LoginLdap
2015-11-05 02:49:48
1f7a8
UserSynchronizer::makeConfigured: configuring with defaultSitesWithViewAccess =
DEBUG
LoginLdap
2015-11-05 02:49:48
1f7a8
UserSynchronizer::makeConfigured(): LDAP access synchronization not enabled.
DEBUG
Piwik\Plugin\Manager
2015-11-05 02:49:48
1f7a8
Loaded plugins: CorePluginsAdmin, CoreAdminHome, CoreHome, WebsiteMeasurable, Diagnostics, CoreVisualizations, Proxy, API, ExamplePlugin, Widgetize, Transitions, LanguagesManager, Actions, Dashboard, MultiSites, Referrers, UserLanguage, DevicesDetection, Goals, Ecommerce, SEO, Events, UserCountry, VisitsSummary, VisitFrequency, VisitTime, VisitorInterest, ExampleAPI, ExampleRssWidget, Feedback, Monolog, UsersManager, SitesManager, Installation, CoreUpdater, CoreConsole, ScheduledReports, UserCountryMap, Live, CustomVariables, PrivacyManager, ImageGraph, Annotations, MobileMessaging, Overlay, SegmentEditor, Insights, Morpheus, Contents, BulkTracking, Resolution, DevicePlugins, Heartbeat, Intl, LogViewer, LoginLdap
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the LoginLdap log entries through Auth\Base::tryFallbackAuth, authenticateByPassword, and UserSynchronizer::makeConfigured. Reproduce the configuration failure with debug logging and determine what configuration or execution path causes the “LDAP access synchronization not enabled” message; done means the LDAP configuration completes without that failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- authentication
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100