Skip to content
This repository has been archived by the owner on Apr 24, 2020. It is now read-only.

Can not add AD #13

Open
TravisWilder opened this issue Jan 17, 2020 · 6 comments
Open

Can not add AD #13

TravisWilder opened this issue Jan 17, 2020 · 6 comments

Comments

@TravisWilder
Copy link

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

@stevebauman
Copy link
Member

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.

@TravisWilder
Copy link
Author

Ok .. let me know if you need help or testing
I already started something similar, but you did better - so I wanted to switch

@stevebauman
Copy link
Member

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 😄

@TravisWilder
Copy link
Author

One small comment: the name .. it is overlapping with Laravel Scout
May be it makes sense to find something more unique (inspector / tracker / auditor)

@stevebauman
Copy link
Member

stevebauman commented Jan 17, 2020

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.

@stevebauman
Copy link
Member

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 scout is already a package from the Laravel core (along with many other packages). This would have created conflicts and would cause this application to be hard to find in search providers (Google / Bing etc.).

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!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants