Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.
If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!
Debug why a user cant login
-
Not quite. It allows users to login that were in the group at the time ProGet was installed. Users added to that same group after that time cant login. the server has been restarted many times.
-
ProGet does not "sync" users/groups from Active Directory.
When an authenticated user (either via name/password or Windows Integrated Auth) accesses ProGet, AD is queried to discover the user's groups. This is cached in memory, but can be cleared by restarting the web application.
Then, permissions are resolved against the user and the groups returned from AD.
So, it really doesn't matter when they were added to the group.
-
Then what is the problem?
-
Short of running something to intercept the LDAP queries and diagnosing from there, there's nothing further we can do on the ProGet side.
One option is, we can share with you the user directory code that ProGet uses to query LDAP, and you can build a simple console application out of the code to see why it won't work for that user.
If that's a direction you'd like to go, please fill out the source request form, and we can send it along.
-
Since the product is unusable and you cannot support it, I would just like a refund. i dont have time to debug your code.
-
The problem is not our code or product, at all; we have 1000's of customers who have absolutely no problem whatsoever using this core functionality.
The problem is your network/configuration, and more specifically, your unwillingness to debug your own network/configuration problems. Expecting us to support your internal network configuration is like expecting Toyota to teach you how to drive a car.
That said, because not everyone knows how to set-up/configure a Windows domain, we offer a full-featured, 45-day trial just to make sure it works on their network. You took advantage of this trial... and then did an extended 90-day trial, and we provided you additional amount of support just getting basic things like IIS set-up.
We absolutely support our product, but you also need to be willing to troubleshoot your own network/configuration problems.
-
There are 10,000 machines and countless servers that authenticate against this domain and multiple servers that use the same groups I am trying to use in ProGet, why is your software the only one that doesn't work?
-
Short of using a crystal ball, we have absolutely no way of knowing why. It is, most certainly, a network/configuration issue on your end.
You need to provide actual information about your network/configuration and what specifically isn't working, in order for us (or anyone else) to provide assistance. This will require you to do additional troubleshooting/investigating to find out why some things work, and some things don't.
Your problem went from "one of our users cant login either using WIA or username and password" to "users to login that were in the group at the time ProGet was installed". Those are two very different problems, and as Alana explained, ProGet does not sync groups... so when the user was added to the group will have no bearing.
-
It's a very simple problem. The NuGet share is configured to allow all members of a certain group read access. This worked during our trial. Since we purchased the license, we added more people to that group. None of the people added since purchasing the license can login. If I add that same user by name in ProGet, he can login. These users have no problem logging in into any other service. Unlike any other server I manage, ProGet provides no information whatsoever about why the login was denied. Normally software records the LDAP response code received from the server in the audit logs.
-
Unfortunately, there's nothing we can log.
We simply ask Active Directory for a user with the specified name and password (using DirectoryEntry), and the DirectorySearcher either returns a user entry, or not. If there was an error while attempting the operation, then it would have been logged.
You can, however, use a third-party tool that operates between the API layer we use and your Active Directory. Microsoft provides Insight for Active Directory, which should be helpful on this.
-
You recommenced ADInsight previously. It is an obsolete tool that is no longer maintained. It does not work in Windows 2008 R2 nor on machines with VMWare tools installed.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login