COmanage Users List

[Benn Oshrin <>]

Hi Kevin,

This is a known issue:

 https://bugs.internet2.edu/jira/browse/CO-1397

We're hoping to get this fixed in the patch release (2.0.1) after the
new feature release (2.0.0) due out in the next couple of days.

There is also an RFE for handling SSH keys as part of enrollment, though
that wouldn't really solve the issue as you point out.

 https://bugs.internet2.edu/jira/browse/CO-1087

Thanks,

-Benn-

On 4/7/17 10:58 AM, Kevin M. Hildebrand wrote:
> I'm using self-signup, LDAP provisioning, and also trying to manage SSH
> public keys.  The problem that I'm having is that the ldapPublicKey
> object class lists sshPublicKey as a required attribute.  So if I enable
> the ldapPublicKey object class in my LDAP provisioner settings, the
> provisioning of new users will fail since there's no way for them to
> initially provide their public key during enrollment.
> 
> Any thoughts on how to deal with this? 
> 1) modify the LDAP schema to make sshPublicKey optional
> 2) modify the LDAP provisioner to not include the ldapPublicKey object
> class if there are no SSH keys defined
> 3) modify the enrollment process to allow upload of SSH keys during sign up
> 
> It seems to me that even if (3) occurs, there may still be times where
> some users might not have SSH keys defined while others do.
> 
> Thanks,
> Kevin
> 
> --
> Kevin Hildebrand
> University of Maryland, College Park