samotelf
commented
5 years ago Hi @snipe I can test this. How can I pull the development version in my PP environment?
Closed snipe closed 5 years ago
samotelf
commented
5 years ago Hi @snipe I can test this. How can I pull the development version in my PP environment?
snipe
commented
5 years ago Awesome, thanks! You'll probably want a clean VM (or however you have your environment set up). Clone the repo, and then git pull develop, and run migrations. So basically, a regular install, but you want to be working from the develop branch)
rklingaman
commented
5 years ago Was looking to test this and got a new instance all setup just like my old one and then tested to make sure I got logged in locally to it. (all was fine)
Then ran the following: git checkout develop composer install --prefer-source composer dump-autoload php artisan migrate php artisan config:clear php artisan config:cache
And now getting error: In LdapAdConfiguration.php line 88:
Your app key has changed! Could not decrypt LDAP password using your curren t app key, so LDAP authentication has been disabled. Login with a local acc ount, update the LDAP password and re-enable it in Admin > Settings.
snipe
commented
5 years ago I have a temp fix on develop for that now
rklingaman
commented
5 years ago Thanks got in it now and so far this is what I see:
Checkboxes are not visable:
The checkboxes did work though and I was able to set it up and test successfully. One thing I see initially on this screen is if I go to using "Active Directory" I don't see a way to toggle between ldap and ldaps or port 389 and 636.
When I go to people and try to do an LDAP sync I come up with this:
Symfony\Component\Console\Exception\CommandNotFoundException thrown with message "The command "snipeit:ldapAd-sync" does not exist."
Stacktrace:
snipe
commented
5 years ago Checkboxes are not visable:
What browser are you using?
snipe
commented
5 years ago (Also are there any other errors in your browser console? I can't reproduce the checkboxes not loading)
rklingaman
commented
5 years ago Was using firefox or Chrome latest versions and happening in both of them. I will play around with it more tomorrow to see if I can dig up why as it seems there are more checkboxes / circles that are disappearing for me besides the ldap ones. Should add that If I refresh I see them for a second before going away.
I did get an LDAP sync to go through with your change so now I will need to test authentication as well.
samotelf
commented
5 years ago I also have the checkboxes problem. I've noticed that if you refresh a lot you can see the checkboxes rendered properly. Anyhow, soon to test ldap.
smb
commented
5 years ago Checkboxes are fixed in https://github.com/snipe/snipe-it/pull/6533/commits/05b326f4c86ca4f269ba541a7e338f61f76974ee but you need to re-run "npm run production" to copy the png files (public/css/*.png should be commited, but there are still some other bugs..)
stale[bot]
commented
5 years ago Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail. This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!
stale[bot]
commented
5 years ago This issue has been automatically closed because it has not had recent activity. If you believe this is still an issue, please confirm that this issue is still happening in the most recent version of Snipe-IT and reply to this thread to re-open it.
Thanks to a great PR from @jwhulette, we're well on our way to making LDAP less frustrating in Snipe-IT in v5. We've tested this locally, but could definitely use some help from those of you who have Snipe-IT running with LDAP or AD.
LDAP and AD are always a challenge to test, since different business cases mean different setups for everyone, so it can be a real challenge to try to test every possible case. This is where you come in!
If you can spare the time/resources/etc to set up a test instance with the
developbranch, we'd love for you to kick the tires a little more, especially if you have less common cases like very large OUs, unusual directory structures, etc.This should absolutely not be used in production yet.
The develop branch, while usually somewhat stable, should never be used in a production environment. That's why it's called
develop😁Remember that the develop branch requires PHP 7.1 or greater.
Would love any feedback you have on the LDAP/AD changes here.