LDAP - Revision history

Shin at 05:32, 14 May 2021

2021-05-14T05:32:18Z

Shin at 01:12, 7 April 2021

2021-04-07T01:12:12Z

Shin at 01:10, 7 April 2021

2021-04-07T01:10:05Z

Shin at 09:32, 6 April 2021

2021-04-06T09:32:14Z

Shin at 09:31, 6 April 2021

2021-04-06T09:31:44Z

Shin: Shin moved page LDAP 인증 to LDAP

2021-04-06T09:17:26Z

Shin moved page LDAP 인증 to LDAP

Shin at 06:00, 3 March 2021

2021-03-03T06:00:42Z

Shin at 05:59, 3 March 2021

2021-03-03T05:59:58Z

Shin at 05:59, 3 March 2021

2021-03-03T05:59:07Z

Shin at 02:43, 3 March 2021

2021-03-03T02:43:49Z

← Older revision		Revision as of 05:32, 14 May 2021
Line 5:		Line 5:
	Similarly to the Pass-Through Authentication, the imRAD decrypts the password in the ACCESS-REQUEST from a user, and then refers to an LDAP server. If an ACCESS-REQUEST is encrypted to an EAP method of which can not decrypt the User-Password attribute, the imRAD RADIUS can not get the correct result.		Similarly to the Pass-Through Authentication, the imRAD decrypts the password in the ACCESS-REQUEST from a user, and then refers to an LDAP server. If an ACCESS-REQUEST is encrypted to an EAP method of which can not decrypt the User-Password attribute, the imRAD RADIUS can not get the correct result.

−	Note that there is no limitation of the LDAP servers but the more LDAP servers, the more time it may take to validate users.	+	{{note\|Note that there is no limitation of the LDAP servers but the more LDAP servers, the more time it may take to validate users.}}

@@ Line 29: / Line 29: @@
 |-
 |}
 ===== LDAP URI =====

@@ Line 12: / Line 12: @@
 {| class="wikitable"
-! 이름 !! 필수 !! 설명
+! Item !! Required !! Description
 |-
-| Primary instance 주소 || 예 || LDAP 서버의 IP 주소를 입력하세요.<br>LDAP over SSL일 경우 ldaps://a.b.c.d와 같은 형식으로 입력하세요. <br>추가 prefix는 아래 LDAP URI를 참고하세요.
+| style='width:250px' | Server1 || Yes || Input the address(e.g, a.b.c.d) or URI(e.g. ldap://myldap.test.org) of a LDAP Server. If the LDAP server supports LDAP over SSL, input the address with a prefix(i.e. ldaps://a.b.c.d). More prefixes are described in the "LDAP URI" section.
 |-
-| Secondary instance 주소 || 아니오 || LDAP 서버의 Secondary instance IP 주소를 입력하세요.<br>LDAP over SSL일 경우 ldaps://a.b.c.d와 같은 형식으로 입력하세요. <br>추가 prefix는 아래 LDAP URI를 참고하세요.
+| Server2  || No || If there is another instance of the LDAP server, input the second server address or URL.
 |-
-| LDAP Server 포트 || 예 || LDAP 서버 포트(기본 포트 389)를 입력하세요.
+| Port || Yes || It is the port of LDAP server(i.e. 389).
 |-
-| Identity of administrator account<br>Password of administrator account  || 아니오 || 일부 LDAP 서버는 User-Name을 조회 할 때 Administrator account를 요구 하므로<br>그 Administrator account의 ID와 Password를 입력하세요.
+| Identity of administrator account<br>Password of administrator account  || No || Some LDAP server requires an administrator account before searching.
 |-
-| Base distinguished name(dn)|| 예 || User-Name 조회시 시작이되는 기본 DN을 입력하세요.
+| Base Distinguished Name(dn)|| Yes || The dn from which all searches will start from.
 |-
-| LDAP server type || 예 || 지정된 LDAP 형식 중 하나를 선택하세요.
+| Server Type || Yes || Choose one of them.
 |-
-| User filter attribute name<br> Group filter attribute name || 예 || 아래 filter attribute name을 참고하세요.
+| User filter attribute name<br> Group filter attribute name || Yes || These values are set automatically according to a selected server type. If you select the server type as "others", you must confirm the User filter attribute name and the Group filter attribute name.
 |-
 |}
@@ Line 36: / Line 36: @@
 ldapc:// (Connectionless LDAP)<br>
-===== filter attribute name =====
+===== Filter Attribute Name =====
 {| class="wikitable"
 ! LDAP Server type !! User filter !! Group filter
@@ Line 50: / Line 50: @@
 |}
-===== LDAP 연결 시험 =====
+===== LDAP Try =====
-생성된 LDAP은 수 분후에 자동으로 그 연결이 올바른지가 확이되나 즉시 User-Name과 User-Password를 시험 하려면 LDAP 목록 우측의 연결 시험 항목의 "연결" 버튼을 클릭하면 "연결 시험" 인터페이스를 열 수 있습니다.<br>
+You can test an LDAP server connection and search for a user after adding a server by click the "connect" button on a list.
 {| class="wikitable"
 ! 메시지 !! 설명
 |-
-| ldap_bind(): Unable to bind to server: Can't contact LDAP server || 서버에 연결 수 없는 경우 표시됩니다.
+| ldap_bind(): Unable to bind to server: Can't contact LDAP server || A server address or URI is incorrect.
 |-
-| ldap_bind(): Unable to bind to server: Invalid credentials || 입력한 사용자 아이디/비밀번호나 저장된 administrator account가 <br>다를 경우 발생합니다.
+| ldap_bind(): Unable to bind to server: Invalid credentials || A test account or an administrator account is incorrect.
 |-
-| success || 성공
+| success || success
 |}

← Older revision		Revision as of 09:32, 6 April 2021
Line 6:		Line 6:

	Note that there is no limitation of the LDAP servers but the more LDAP servers, the more time it may take to validate users.		Note that there is no limitation of the LDAP servers but the more LDAP servers, the more time it may take to validate users.
		+

	==== Edit LDAP Server ====		==== Edit LDAP Server ====

@@ Line 1: / Line 1: @@
 __FORCETOC__
-=== RADIUS > 설정 > LDAP 인증 ===
+=== RADIUS > Settings > LDAP ===
-외부에 존재하는 LDAP(Lightweight Directory Access Protocol) 서버를 통해 인증을 처리 할 경우 그 서버를 정의 할 수 있습니다.<br>
+Note that there is no limitation of the LDAP servers but the more LDAP servers, the more time it may take to validate users.
-[[RADIUS 개요]]에서 언급한 바와 같이 OpenLDAP과 Microsoft Active Directory(AD)에 연결해 사용자를 인증 할 수 있습니다.<br>
-등록 할 수 있는 개수는 제한이 없으나 imRAD에 수신된 User-Name/User-Password가 모든 LDAP을 거쳐 확인 되는 과정이 반복되므로 너무 많은 LDAP 서버를 등록하면 성능 하락의 원인이 될 수 있습니다.
+==== Edit LDAP Server ====
 {| class="wikitable"
 ! 이름 !! 필수 !! 설명

@@ Line 57: / Line 57: @@
 | ldap_bind(): Unable to bind to server: Can't contact LDAP server || 서버에 연결 수 없는 경우 표시됩니다.
 |-
-| ldap_bind(): Unable to bind to server: Invalid credentials || 입력한 사용자 아이디/비밀번호가 올바르지 않거나 서버의 administrator account가 다를 경우 발생합니다.
+| ldap_bind(): Unable to bind to server: Invalid credentials || 입력한 사용자 아이디/비밀번호가 올바르지 않거나<br>서버의 administrator account가 다를 경우 발생합니다.
 |-
 | success || 성공
 |}

@@ Line 45: / Line 45: @@
 | Others || User defined || User defined
 |-
 |}