Difference between revisions of "SAC Service Status"

From OSGeo
Jump to: navigation, search
(Known Issues)
Line 17: Line 17:
 
* We have to create userids on the LDAP server manually, can't be done through plone without a lot of work.
 
* We have to create userids on the LDAP server manually, can't be done through plone without a lot of work.
 
* Plone instance is not using LDAP for authentication.
 
* Plone instance is not using LDAP for authentication.
 +
 +
== Service Groups ==
 +
 +
Currently, shell access is limited to users in the LDAP schema under the "Shell" group.  No further
 +
group authorization/granularity exists at this time.  It is desireable to have "Shell" be
 +
broken into groups like "Database", "Subversion Admin", etc to distribute the administration of
 +
those tasks.

Revision as of 20:50, 22 June 2006

System List

Telascience Blades

  • osgeo.telascience.org (198.202.74.211): Contains plone installation
  • ldap.telascience.org (198.202.74.220): FC4 + Fedora Directory Server. Contains LDAP server.
  • shell server (198.202.74.218): FC4. Lots of software installed, general use.

Services

  • LDAP (on .74.220)

Known Issues

  • .74.211 is not using ldap authentication for shell access.
  • .74.220 is not using ldap authentication for shell access.
  • Access to LDAP server needs to be restricted to specific machines somehow?
  • We have to create userids on the LDAP server manually, can't be done through plone without a lot of work.
  • Plone instance is not using LDAP for authentication.

Service Groups

Currently, shell access is limited to users in the LDAP schema under the "Shell" group. No further group authorization/granularity exists at this time. It is desireable to have "Shell" be broken into groups like "Database", "Subversion Admin", etc to distribute the administration of those tasks.