It turns out that the plugin hardwires the use of "@" as a separator
between the mcf user name and the mcf domain.  Unfortunately, this prevents
the mcf user name from containing an "@", which is necessary for Active
Directory.

I'm going to propose just changing this unfortunate choice of character
from "@" to ":".  Using the colon will mean that unless there's an actual
user name with a ":" in it we won't have this problem again.

I know it's not backwards compatible, but frankly the plugin could not work
properly in the form it is currently in.  And it's a relatively new plugin
too (less than six months old).

Thoughts?

Karl

Reply via email to