-
Notifications
You must be signed in to change notification settings - Fork 3
Can not add AD #13
Comments
Hi @TravisWilder, thanks for the report! I'll leave this open so I know to work on it, but Scout is not ready for use - you will encounter many bugs and issues. It's not even in alpha state. A GitHub release will be created when it is ready for alpha / beta. |
Ok .. let me know if you need help or testing |
Thanks for your kind words! ❤️ Really appreciate it. I'm really excited about Scout - I've been wanting to build it for a long time. It's something I've been needing for a while and there's nothing good out there that is free (in my opinion). I'll absolutely let you know if I need some help testing 😄 |
One small comment: the name .. it is overlapping with Laravel Scout |
Thanks for the suggestion, though I'm set on the name. I've already purchased logo + assets for the application that have not yet been implemented. |
Okay - I've thought about this a lot @TravisWilder, and I now agree with you. I've decided to create a installable composer package and rename this application to Watchdog, instead of Scout. I wanted to have publishable configuration files, but of course as you've mentioned, the name I'm wanting to make this thing as flexible as possible. Having it pre-built as an application caused me issues trying to extend it, so it is going to be installable into any Laravel application, which allows it to be easily updatable using composer. I appreciate your input! |
Hello,
adding an ad is failing.
I use on the same server a Laravel installation with Adldap2 which works fine with the same settings.
ActiveDirectory
SSL
Port 636
Response is always: ldap_bind(): Unable to bind to server: Can't contact LDAP server
Does not change if I use only one hostname or IP
looking also forward on the LdapRecord-Laravel documentation
bye
Travis
The text was updated successfully, but these errors were encountered: