Authentication DB - Revision history

Shin: /* RADIUS > Settings > Authentication Database */

2023-08-09T05:23:07Z

RADIUS > Settings > Authentication Database

Shin: /* Edit Database connection attributes */

2023-08-09T05:21:52Z

Edit Database connection attributes

Shin at 05:14, 9 August 2023

2023-08-09T05:14:30Z

Shin: Shin moved page Authentication Database to Authentication DB

2023-08-09T05:01:57Z

Shin moved page Authentication Database to Authentication DB

Shin at 05:01, 9 August 2023

2023-08-09T05:01:47Z

Shin: Shin moved page Pass-Through Authentication (PTA) to Authentication Database

2023-08-09T04:34:31Z

Shin moved page Pass-Through Authentication (PTA) to Authentication Database

Shin at 05:40, 16 April 2021

2021-04-16T05:40:04Z

Shin at 09:34, 6 April 2021

2021-04-06T09:34:49Z

Shin at 09:33, 6 April 2021

2021-04-06T09:33:32Z

Shin at 09:32, 6 April 2021

2021-04-06T09:32:55Z

@@ Line 1: / Line 1: @@
 __FORCETOC__
-=== RADIUS > Settings > Authentication Database ===
+=== RADIUS > Settings > Authentication DB ===
-The authentication database that stores user authentication information (User-Name / User-Password) consists of an internal database (local) within the imRAD N1 system and a customer database (external). When a user authentication request is received, the system checks the authentication locally in the database, and if the user is not found, it proceeds to authenticate against the external database.
+The authentication DB(Database) that stores user authentication information (User-Name / User-Password) consists of an internal database (local) within the imRAD N1 system and a customer database (external). When a user authentication request is received, the system checks the authentication locally in the database, and if the user is not found, it proceeds to authenticate against the external database.
 ==== Local Database ====

@@ Line 51: / Line 51: @@
 | Database || Yes || If a DBMS is Oracle, Input a SID. Otherwise, input the name of database or schema that executes a stored function.
 |-
-| PTA Query  || Yes || Input a query to validate a user. Please refer to the below "Stored Function examples" for details.
+| Query  || Yes || Input a query to validate a user. Please refer to the below "Stored Function examples" for details.
 |-
 |}

@@ Line 4: / Line 4: @@
 ==== Local Database ====
-This is the information for radiusd (RADIUS daemon service) to connect to the local database, and there is no need to modify it as it will change automatically when redundancy is configured. If the connection to the local database fails, you can store the password again and click the 'Connection Test' button to verify.
+This is the information for radiusd (RADIUS daemon service) to connect to the local database, and there is no need to modify it as it will change automatically when redundancy is configured. If the connection to the local database fails, you can store the password again and click the 'Connection Test' button to verify.<br>
 ==== External Database ====
-A pass-through authentication enables the RADIUS server to confer with another entity(e.g. windows security database, oracle, and so on) to validate the user's username and password.<ref>Jim Geier, Implementing 802.1X Security Solutions for Wired and Wireless Networks</ref>
+The imRAD N1 can directly connect to a customer database, and then executes a query to authenticate users.
+By this setting, users can be authenticated without migration all user information from a customer database to the imRAD N1 database.<br>
 You can add up to 4 entities and we support the following.
 <pre>
@@ Line 27: / Line 27: @@
 If an ACCESS-REQUEST is encrypted to an [[RADIUS Authentication testing | EAP method ]] of which can not decrypt the User-Password attribute, the imRAD RADIUS can not get the correct result.
-If more than 2 PTAs exist, the imRAD RADIUS executes each query until validate a user.
+If more than 2 external databases exist, the imRAD RADIUS executes each query until authenticate a user.
+{{note|When an external database is added, the connection status will automatically change within 1 minute.}}
-==== Edit PTA ====
+=====Edit Database connection attributes =====
-You can add a new entity by click "Add" button at the right bottom below the PTA list. If there are 4 entities, It does not show the "Add" button. If you want to change or delete a entity, click the [[File:popup.png]] icon in front of each entity.
+You can add a new entity by click "Add" button at the right bottom below the list. If there are 4 entities, It does not show the "Add" button. If you want to change or delete an entity, click the [[File:popup.png]] icon in front of each entity.
 {| class="wikitable"
 ! Item!! Required !! Description

@@ Line 1: / Line 1: @@
 __FORCETOC__
-=== RADIUS > Settings > PTA ===
+=== RADIUS > Settings > Authentication Database ===
 A pass-through authentication enables the RADIUS server to confer with another entity(e.g. windows security database, oracle, and so on) to validate the user's username and password.<ref>Jim Geier, Implementing 802.1X Security Solutions for Wired and Wireless Networks</ref>

← Older revision		Revision as of 05:40, 16 April 2021
Line 65:		Line 65:
	* NAS-Identifier: If you choose a NAS-Identifier, an ACCESS-REQUEST only from the [[NAS Identifier \| NAS-Identifier]] passes to this PTA. In other words, It does not refer to the remote database to validate users who requested from other NAS-Identifiers.		* NAS-Identifier: If you choose a NAS-Identifier, an ACCESS-REQUEST only from the [[NAS Identifier \| NAS-Identifier]] passes to this PTA. In other words, It does not refer to the remote database to validate users who requested from other NAS-Identifiers.

−		+	=== References ===
−	~~<br><hr>~~

← Older revision	Revision as of 04:34, 9 August 2023
(No difference)

@@ Line 3: / Line 3: @@
 A pass-through authentication enables the RADIUS server to confer with another entity(e.g. windows security database, oracle, and so on) to validate the user's username and password.<ref>Jim Geier, Implementing 802.1X Security Solutions for Wired and Wireless Networks</ref>
-The imRAD directly connects to a customer database, and then executes a query to validate users.
+The imRAD directly connects to a customer database, and then executes a query to validate a user.
-By this setting, users can be authenticated without migration the user information from a customer database to the imRAD database.<br>
+By this setting, a user can be authenticated without migration the user information from a customer database to the imRAD database.<br>
 You can add up to 4 entities and we support the following.
 <pre>