OpenLDAP에서 MD5를 인증에 사용하는 방법은 무엇입니까?


1

AWS에 OpenLDAP를 설치했는데 사용자 인증을 시도 할 때까지 모든 것이 예상대로 작동했으며 암호를 묻고 암호를 입력하면 Permission denied, please try again.일반 텍스트와 MD5의 패스로 시도했지만 무슨 일이 일어나고 있는지 모르겠습니다 ... 사용자가 암호로 인증 할 수 있도록 구성을 수정했습니다 ... 파일이나 무언가가 필요하면 질문하고 업데이트하십시오. 감사합니다!

최신 정보:

이것은 리눅스 인증을위한 것입니다

# This is the main slapd configuration file. See slapd.conf(5) for more
# info on the configuration options.

#######################################################################
# Global Directives:

# Features to permit
#allow bind_v2

# Schema and objectClass definitions
include         /etc/ldap/schema/core.schema
include         /etc/ldap/schema/cosine.schema
include         /etc/ldap/schema/nis.schema
include         /etc/ldap/schema/inetorgperson.schema

# Where the pid file is put. The init.d script
# will not stop the server if you change this.
pidfile         /var/run/slapd/slapd.pid

# List of arguments that were passed to the server
argsfile        /var/run/slapd/slapd.args

# Read slapd.conf(5) for possible values
loglevel        none

# Where the dynamically loaded modules are stored
modulepath  /usr/lib/ldap
moduleload  back_@BACKEND@

# The maximum number of entries that is returned for a search operation
sizelimit 500

# The tool-threads parameter sets the actual amount of cpu's that is used
# for indexing.
tool-threads 1

#######################################################################
# Specific Backend Directives for @BACKEND@:
# Backend specific directives apply to this backend until another
# 'backend' directive occurs
backend     @BACKEND@

#######################################################################
# Specific Backend Directives for 'other':
# Backend specific directives apply to this backend until another
# 'backend' directive occurs
#backend        <other>

#######################################################################
# Specific Directives for database #1, of type @BACKEND@:
# Database specific directives apply to this databasse until another
# 'database' directive occurs
database        @BACKEND@

# The base of your directory in database #1
suffix          "@SUFFIX@"

# rootdn directive for specifying a superuser on the database. This is needed
# for syncrepl.
# rootdn          "cn=admin,@SUFFIX@"

# Where the database file are physically stored for database #1
directory       "/var/lib/ldap"

# The dbconfig settings are used to generate a DB_CONFIG file the first
# time slapd starts.  They do NOT override existing an existing DB_CONFIG
# file.  You should therefore change these settings in DB_CONFIG directly
# or remove DB_CONFIG and restart slapd for changes to take effect.

# For the Debian package we use 2MB as default but be sure to update this
# value if you have plenty of RAM
dbconfig set_cachesize 0 2097152 0

# Sven Hartge reported that he had to set this value incredibly high
# to get slapd running at all. See http://bugs.debian.org/303057 for more
# information.

# Number of objects that can be locked at the same time.
dbconfig set_lk_max_objects 1500
# Number of locks (both requested and granted)
dbconfig set_lk_max_locks 1500
# Number of lockers
dbconfig set_lk_max_lockers 1500

# Indexing options for database #1
index           objectClass eq

# Save the time that the entry gets modified, for database #1
lastmod         on

# Checkpoint the BerkeleyDB database periodically in case of system
# failure and to speed slapd shutdown.
checkpoint      512 30

# The userPassword by default can be changed
# by the entry owning it if they are authenticated.
# Others should not be able to see it, except the
# admin entry below
# These access lines apply to database #1 only
access to attrs=userPassword,shadowLastChange
    by dn="@ADMIN@" write
    by anonymous auth
    by self write
    by * none

# Ensure read access to the base for things like
access to dn.base="" by * read

access to *
    by dn="@ADMIN@" write
    by * read

(1) 어떤 서비스를 인증하고 있습니까? 이메일 (dovecot / posttfix)? 리눅스 로그인? HTTP? (2) slapd.conf가 필요할 수 있습니다.
John Siu

@JohnSiu 완료, 그것은 업데이 트되었습니다 ... 이것은 리눅스 로그인입니다 ...
poz2k4444

아직 테스트 할 시간이 없습니다. 그러나 PAM도 구성 했습니까?
John Siu

@JohnSiu 그래, 나는 달렸다sudo pam-auth-update
poz2k4444

이 길드 를 사용 했습니까 ? 지금 통과하려고합니다.
John Siu

답변:


1

참조 링크

1. 할 dpkg-reconfigure slapd

dpkg-reconfigure slapd

다음 답변 사용

Omit OpenLDAP server configuration? No
DNS domain name: testlab.dev
Organization name: testlab.dev
Administrator password: <password>
Confirm password: <password>
Database backend to use: BDB or HDB(prefered)
Do you want the database to be removed when slapd is purged? Yes/No (your choice)
Move old database? Yes (clean start)
Allow LDAPv2 protocol? No

2. libnss-ldap이 있는지 확인하십시오

apt-get install libnss-ldap

3. 할 dpkg-reconfigure ldap-auth-config

dpkg-reconfigure ldap-auth-config

다음 답변 사용

Should debconf manage LDAP configuration? Yes
LDAP server Uniform Resource Identifier: ldapi:///
Distinguished name of the search base: dc=testlab,dc=dev
LDAP version to use: 3
Make local root Database admin: Yes
Does the LDAP database require login? No
LDAP account for root: cn=admin,dc=testlab,dc=dev
LDAP root account password: <password>
Local crypt to use when changing passwords: md5

4. 이제 NSS에 대한 LDAP 프로파일을 구성하십시오.

auth-client-config -t nss -p lac_ldap

5. 인증을 위해 LDAP를 사용하도록 시스템을 구성하십시오.

sudo pam-auth-update

[*] LDAP Authentication가 선택되어 있는지 확인하십시오 .


위의 단계 후에 ldap 사용자를 다시 작성해야합니다.
John Siu

글쎄 ... 지금 바보 같은 느낌, 당신이 다른 것을 사용하는 유일한 LDAP server Uniform Resource Identifier: ldapi:///이유 는 왜 작동하지 ldap://127.0.0.1않습니까 ??
poz2k4444

나도 확실하지 않다. 오늘 밤 더 많은 연구를 할 계획입니다. 또한 LDAP 서버 연결을 localhost로만 제한하는 방법을 찾아야합니다. 위의 구성은 모든 인터페이스에서 수신 대기 중이며 매우 안전하지 않습니다.
John Siu

글쎄 .. 어떻게해야할지 알 것 같아 ... 원격으로 연결해야하기 때문에 ...
poz2k4444
당사 사이트를 사용함과 동시에 당사의 쿠키 정책개인정보 보호정책을 읽고 이해하였음을 인정하는 것으로 간주합니다.
Licensed under cc by-sa 3.0 with attribution required.