Grouper Developers Forum

[Gagné Sébastien <>]

Great news indeed.
We've been waiting for 2.1.2 for our tests, were planning on synching 10 000 
groups at once to Active Directory.

I'm still waiting to get our dev environment back from a catastrophic 
failure, then I'll upgrade Grouper to 2.1.2 (from 2.1.0) and try the new PSP. 
I think I'll be able to do a first run beginning of next week.

-----Message d'origine-----
De : 

 
[mailto:]
 De la part de Tom Barton
Envoyé : 29 août 2012 17:18
À : 

Objet : Re: [grouper-dev] another psp 2.1.2 release candidate

TomZ, this is great news.

Folks, is there a campus that's been waiting on this that might be able to 
validate it in their test environment pretty soon?

Thanks,
TomB

On 8/29/2012 3:36 PM, Tom Zeller wrote:
> Another psp 2.1.2 release candidate is now available.
>
>   http://www.internet2.edu/grouper/release/2.1.2/
>
> A pretty horrible bug was introduced in 2.1.1 which catastrophically 
> deletes all provisioned objects when provisioning Active Directory.
> Hence, I disabled downloads of 2.1.1.
>
> The psp considers identifiers to be case sensitive, and defaults to 
> lowercase rdn attribute types, for example
>
>   dc=example,dc=edu
>
> while Active Directory returns uppercase rdn attribute types, for 
> example
>
>   DC=example,DC=edu
>
> The difference between uppercase and lowercase rdn attribute types 
> resulted in the psp incorrectly deleting provisioned objects.
>
> When provisioning Active Directory, care should be taken to make sure 
> that ldap dns are calculated with uppercase rdn attribute types. Prior 
> to version 2.1.2, rdn attribute types were not configurable when 
> calculating ldap dns from grouper names. This 2.1.2 release candidate 
> allows rdn attribute types to be configured, for example
>
>    <resolver:AttributeDefinition
>      id="groupDn"
>      xsi:type="psp-grouper-ldap:LdapDnFromGrouperNamePSOIdentifier"
>      rdnAttributeName="CN"
>      stemRdnAttributeName="OU"
>      ... />
>
> At first I thought that comparing identifiers case-insensitively was 
> the right thing to do, but the openspml library uses string equals() 
> to compare identifiers, and I decided this would be messy to override.
> So for now, identifiers are case sensitive.
>
> Changes made in version 2.1.1 to improve performance exposed this 
> issue. I hurried 2.1.1 without adequate testing. It took a while to 
> acquire another Active Directory test environment, mostly because of 
> my schedule.
>
> Thanks for your patience,
> and apologies for the inconvenience,
> TomZ