Skip to Content.
Sympa Menu

comanage-dev - Re: [comanage-dev] posixAccount (CO-863) and ldapPublicKey (CO-864)

Subject: COmanage Developers List

List archive

Re: [comanage-dev] posixAccount (CO-863) and ldapPublicKey (CO-864)


Chronological Thread 
  • From: Benn Oshrin <>
  • To: Scott Koranda <>
  • Cc: comanage-dev <>
  • Subject: Re: [comanage-dev] posixAccount (CO-863) and ldapPublicKey (CO-864)
  • Date: Sat, 26 Apr 2014 22:18:37 -0400

Hack the permissions in isAuthorized.

On April 26, 2014 10:17:13 PM EDT, Scott Koranda <> wrote:
Hi,

So I have the SSH demo working. It is pretty sweet.

The only thing missing is a user being able to upload his/her own SSH key.

Is there any way we can work around that for the demo?

Thanks,

Scott


On Mon, Apr 21, 2014 at 9:30 PM, Benn Oshrin <> wrote:
I've just pushed a commit to develop for the HTCondor SSH use case. The
ldapPublicKey is now supported and fully usable... and admin can upload an
SSH key to a CO Person, enable the ldapPublicKey schema in the
LdapProvisioner, and write the key to LDAP.

posixAccount is a bit trickier. We should really have a UnixAccount model,
but for now posixAccount pulls much of what it needs from the Identifiers
model (so you can auto-assign the relevant identifiers). To set this up,
create Extended Types for Identifiers called "gidNumber", "homeDirectory",
and "uidNumber" (case sensitive). Populate these identifiers for your CO
Person (manually or via auto assignment) and enable the posixAccount schema
to write these to LDAP. gecos is constructed from cn and loginShell is
hardcoded to /bin/tcsh.

I should be able to get the homeDirectory provisioner stubbed out in the
next day or two, but in the mean time Scott, you should be able to make some
progress on connecting a VM to LDAP with these changes.

Thanks,

-Benn-



Archive powered by MHonArc 2.6.16.

Top of Page