2

1

We have a large number of users in Active Directory that do not have a FogBugz user (only the information systems staff have users in FogBugz.) Currently, we capture any user which calls in with a problem in a free text Custom Field. This is OK, but doesn't provide us quick access with much of the useful information in Active Directory (such as phone/location/etc.) It also doesn't prevent typos, only the users's name is entered.

I have been considering a plugin which copies some information from LDAP/AD into a table within FogBugz and creating a custom field which allows selection of users (and subsequently presents users with useful information about the associated AD account.)

Unfortunately, because of AppDomain settings this appears to be more difficult than I originally anticipated, I believe .NET provides an easy way to interact with Active Directory in the System.DirectoryServices namespace... when I attempt to access AD information with an instance of DirectoryEntry, FogBugz chokes and throws a SecurityException. Are there plans on allowing the AppDomain settings to be modified?

Also, I know that FogBugz interacts with LDAP/AD for user creation and authentication, are any of those methods exposed so I could access the information from AD that way?

If not... the only alternative I could think of would be to write a separate application and update fogbugz via hits to a raw plugin page... does anyone have any better ideas?

(Little side note here: it would be useful if Community Users could be LDAP/AD as well, we have many users that may wish to collaborate on wikis and discussions but must be manually setup with another username/password for them to remember.)

Fog Creek Case FC1915776

flag

2 Answers

1

We are considering ways to safely open up more power to plugins, but it's a tricky matter. But there is a workaround: you can run your plugin in full-trust mode:

  1. Copy the plugin .dlls to this directory:
        Website/bin/TrustedPluginBin
  2. Set the registry value fRun[YOUR_PLUGIN_ID]InFogBugzAppDomain = "1" under the FogBugz registry key:
        /HKEY_HKEY_LOCAL_MACHINE\SOFTWARE\Fog Creek Software\FogBugz[YOUR FOGBUGZ INSTALL DIR].
        (Your plugin ID is something like CustomFields@fogcreek.com)
link|flag
0

I have opened a feature request for a better way to access LDAP/AD. Please up-vote the question above if you would like to see it implemented in a future version of the Plugin API

link|flag

Your Answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.