BugTracker.NET 2.7.5

Rating: No reviews yet
Downloads: 168
Released: Feb 3, 2008
Updated: Feb 4, 2008 by ctrager
Dev status: -not yet defined by owner-

Recommended Download

Source Code BugTracker.NET 2.7.5
source code, 1419K, uploaded Feb 4, 2008 - 168 downloads

Release Notes

This release adds some LDAP/Active Directory support.

Before deploying this release, you must change your Web.config file.
Your Web.config might be different from mine, but for me, the change
I had to make was from this:

<compilation debug="true"/>

to this:

<compilation debug="true">
<assemblies>
<add assembly="System.DirectoryServices.Protocols, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
</assemblies>
</compilation>


To enable LDAP support, configure these settings in your Web.config:


<!--
You can have BugTracker.NET check the user's password using an LDAP server instead of
checking it in the database. You still have to create a BugTracker.NET user. It's only
the password that get's checked.

To use LDAP, set AuthenticateUsingLdap to 1 and enter the appropriariate distinguished name.
The $REPLACEWITHUSERNAME$ gets replaced with the username that's typed in by the user
when he tries to log on.
-->
<add key="AuthenticateUsingLdap" value="1"/>
<add key="LdapServer" value="127.0.0.1"/>
<add key="LdapUserDistinguishedName" value="uid=$REPLACEWITHUSERNAME$,ou=people,dc=mycompany,dc=com"/>

When you enable LDAP support, the application checks user passwords against the ones stored in your
LDAP directory rather than the ones stored in the database.

The zip also contains sample code for importing users from LDAP into
BugTracker.NET's database. See "importusersfromldapsample.cs".

Also:
  • Fixed bug with duplicate users in user dropdowns that affected
"external" users. Thanks to Suchacek Zdenek for help with this.
  • Fixed how app was handling bugs associated with inactive projects or
inactive users, or users who are no longer marked assignable. Before,
if a bug was assigned to an inactive user, and then you updated the bug
in some other way, you would inadvertently also change the user too,
because the inactive user was missing from the dropdown. Now, the
current project/user is always FORCED into the dropdown, even if
it is inactive.

Reviews for this release

No reviews yet for this release.