Hi,

as described in this post: http://social.technet.microsoft.com/Forums/en-US/sharepointcollaboration/thread/a047b575-7140-48e0-ae1f-14c5d116d8dd I'm having problems with the external users management web part because the password expiration policy is set to 0. I don't have access, nor am I allowed to alter this policy setting since it's company wide. As I understand, there's no other way of configuring this setting apart from altering the global active directory policy (since the server is a domain member). If that's the case; how am I going to make this work? Could someone perhaps send me a version of the webpart which doesn't crash on this bug?

Kind regards,

Jasper

A quick google search tells me that ADAM doesn't support it's own policies; it's not implemented that way.  So the only way to override the domain password policy is to disable it altogether in ADAM with ADAMDisablePasswordPolicies=1

I don't know if that will help you in this situation, though, because I think the exception will still be thrown. 

I think the reason you're not seeing a lot of folks lining up to answer your questions on the ECTS is that it wasn't written by any of the volunteer developers in the CKS, it was developed by the SA-SC team, and the source code turned turned over to the public via the CKS on CodePlex. 

You could, of course, open the source code and fix the issue.  I'm not familiar with the ECTS source, as I've been mostly involved with the CKS:FBA solution, but a brief look at it (via the Source Code tab on this page) tells me the bug is in the PasswordLifetime() method:

if (result.Properties.Contains(val))
{
          // bugbug: math error when no domain PWD policy
          ticks = Math.Abs((long)result.Properties[val][0] );

}

Someone even commented it. 

I suppose if the PasswordLifetime method returned a very large TimeSpan in that case, it would be "good enough".  You could even wrap the math in a try-catch block and set ticks equal to some really large (but supported) number in the catch block. Like Int64.MaxValue.  Not an ideal solution, but probably good enough for now.


Regards,
Mike Sharp

Hi Mike,

thanks for your comments and sorry for the frustration on my part ;) These tips are very helpfull, I'll check if I can manage to edit the sourcecode to fix this problem. As for the support; it's a it odd no one here has worked on these sources, aren't they in the wrong place then?

Kind regards,

Jasper