File: control

package info (click to toggle)
pg-ldap-sync 0.5.1-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 160 kB
  • sloc: ruby: 415; makefile: 4
file content (41 lines) | stat: -rw-r--r-- 1,588 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
Source: pg-ldap-sync
Section: database
Priority: optional
Maintainer: Debian PostgreSQL Maintainers <team+postgresql@tracker.debian.org>
Uploaders: Dominik George <natureshadow@debian.org>
Build-Depends: debhelper-compat (= 13),
               gem2deb (>= 1),
               kwalify,
               rake,
               ruby,
               ruby-net-ldap,
	       ruby-pg
Standards-Version: 4.6.0
Vcs-Git: https://salsa.debian.org/postgresql/pg-ldap-sync.git
Vcs-Browser: https://salsa.debian.org/postgresql/pg-ldap-sync
Homepage: https://github.com/larskanis/pg-ldap-sync
XS-Ruby-Versions: all
Rules-Requires-Root: no

Package: ruby-pg-ldap-sync
Architecture: all
XB-Ruby-Versions: ${ruby:Versions}
Depends: ${misc:Depends},
         ${ruby:Depends},
         ${shlibs:Depends}
Description: Synchronize users and groups from LDAP/AD into PostgreSQL
 LDAP is often used for a centralized user and role management
 in an enterprise environment. PostgreSQL offers different
 authentication methods, like LDAP, SSPI, GSSAPI or SSL.
 However, for any method the user must already exist in the database,
 before the authentication can be used. There is currently
 no direct authorization of database users on LDAP. So roles
 and memberships has to be administered twice.
 .
 This program helps to solve the issue by synchronizing users,
 groups and their memberships from LDAP to PostgreSQL.
 Access to LDAP is used read-only. <tt>pg_ldap_sync</tt> issues proper
 CREATE ROLE, DROP ROLE, GRANT and REVOKE commands to synchronize
 users and groups.
 .
 It is meant to be started as a cron job.