Hi,
we're evaluating Mingle in a real world project and we like it. It's a great tool. However, during a routine check of server access logs, we found out that some process appears to be attempting to hack our repository. It tries every so often and gets turned down by authentication. It looks like a brute force attack to crack the passwords. After a little research, we found out that the process in question is Mingle!
It seems to make little sense, doesn't it? After all we entered the subversion repository access details in the project settings, the repository details are correct and integration works five-by-five.
Now why is Mingle attempting to access our repository in this manner?
Comments
1 comment
Hello - I would like to assure you that Mingle is not trying to hack your Subversion repository. Mingle's source control integration works by querying the version control system with the credentials provided, and pulling data into Mingle for faster access. This work is done in batches, and you will notice the Mingle process logging in successfully to pull data out of Subversion many times a day, provided it is configure correctly.
You say that your source control integration is working fine. This though is a per-project setting. Are there other projects on the same Mingle instance and are they all configured correctly? Perhaps a template that was created from your project that someone else has created a project from? To identify if a project is configured correctly, check to see if you see a "Source" tab in Mingle for the project(s) in question, and if you can navigate to it without problems. Also keep in mind that you have to be a member of a project to see its data. If you are not a member of all projects on the Mingle instance, this may be a task for your Mingle Administrator.
If all the above turn out to be negative, please forward your mingle log files over to our support team, and we can help you identify what project is configured incorrectly.
Please sign in to leave a comment.