ClueNet is looking for a new Chief Technical Admin. More information here.

From ClueWiki

Cluenet accounts are centrally maintained so user information is synchronized. All user information is stored in an LDAP database which can be accessed by users. Users can also use Kerberos for authentication, and all Cluenet servers should support both Kerberos and LDAP authentication.

Cluenet accounts may have different permissions based on the host, authorizedService, and clueAuthorizedAbility LDAP attributes. The combination of values of these LDAP attributes define the permissions that a user has and the services that the user can access. Most Cluenet servers do not filter access based on the host attribute - only the critical, limited-access servers filter based on a user's host attributes. By default, a user has no host attributes, and is not allowed access to the restricted servers. The authorizedService attribute defines which services the user has access to. A user account, right after it is created, has access to the wiki, forum, and other web services, but not to SSH on the servers. The SSH authorizedService is granted based on an additional signup procedure. The clueAuthorizedAbility attribute is a custom attribute specifying fine-tuned access control to Cluenet software.

Basic user accounts are easy to obtain, all that is required is validating an email address and asking an existing user to approve the account, which should be done immediately. The procedure for obtaining shell access is slightly more complicated - you can read about it on the Signing Up page.

More information can be found on the Cluenet Infrastructure and LDAP and LDIFs pages.