Different ComputedID for some (not all) users on 3.2.1?

[Sean Mason]

This appears to be the solution.

Unfortunately I did not have this configuration in place on the current instance of the IdP or the new one, so the only way to make the two generate the same identifier is to configure them both to properly handle the binary AD attribute.  That means I unknowingly shot myself in the foot some time ago, and have just now felt the pain.

Does anyone out there have a bandage in the form of a way to pre-generate Computed IDs for a given service provider and user so I can get those services that have been consuming the mal-formed ID to update to a new one?

Thanks again,
Sean

> -----Original Message-----
> From: users [mailto:users-bounces at shibboleth.net] On Behalf Of Rod
> Widdowson
> Sent: Friday, February 12, 2016 11:18 AM
> To: 'Shib Users' <users at shibboleth.net>
> Subject: RE: Different ComputedID for some (not all) users on 3.2.1?
> 
> Object GUID is binary IIRC, so you need to tell the LDAP connector to "do the
> right thing".
> 
> Something like:
> 
> <dc:LDAPProperty name="java.naming.ldap.attributes.binary" value="objectSid
> objectGUID"/>
> 
> I think, but Daniel will correct me...
> 
> Rod
> 
> --
> To unsubscribe from this list send an email to users-
> unsubscribe at shibboleth.net