move the type of access_class to deployment ( as this is tied to our group name )

1 files changed, 0 insertions, 26 deletions

diff --git a/modules/pam/manifests/init.pp b/modules/pam/manifests/init.pp
index 732957c4..246bb4f6 100644
--- a/modules/pam/manifests/init.pp
+++ b/modules/pam/manifests/init.pp
@@ -47,30 +47,4 @@ class pam {
   define multiple_ldap_access($access_classes) {
     include base
   }
- 
-  # beware , this two classes are exclusives
-  # if you need multiple group access, you need to define you own class
-  # of access  
- 
-  # for server where only admins can connect
-  class admin_access {
-    multiple_ldap_access { "admin_access":
-        access_classes => ['mga-sysadmin']
-    }
-  }
-
-  # for server where people can connect with ssh ( git, svn )
-  class committers_access {
-    # this is required, as we force the shell to be the restricted one
-    # openssh will detect if the file do not exist and while refuse to log the
-    # user, and erase the password ( see pam_auth.c in openssh code, seek badpw )
-    # so the file must exist
-    # permission to use svn, git, etc must be added separatly
-     
-    include restrictshell::shell
-
-    multiple_ldap_access { "committers_access":
-        access_classes => ['mga-commiters']
-    }
-  }
 }