The Authentication User table. Remote dial-in clients can be
authenticated: locally using an internal database, or externally
using a Radius server server. Clients are defined internally
in this table. This table can have a special '
that defines the default user authentication method and
default tunnel name. The table lookup is always done first.
If the client's name is not found a 'default' entry defines
an alternative authentication methanism. If the 'default' entry
is not defined, and the client is not found in the table, the
client is denied access to the network, i.e. IPsec security
associations will not be created. If the client's name is
found in the table, the ipsecRemoteClientAuthenProtocol
defines which authenication mechanism is to be used.
Specific users CAN be excluded by specifying 'always reject'
in the authentication protocol. The 'default' user can be
set to 'always accept' to allow ALL undefined users to
be automatically authenticated.
For 'internal authentication', whether through a specific
entry, or the default entry, the requested password must
match the configured password. '
Remote client example:
xauthUserName = [email protected],
xauthUserPassword = abc,
xauthUserTunnelName = Engineering,
xauthUserAuthenProtocol = internalAuthentication.
Parsed from file xauth.mib.txt
Company: None
Module: XEDIA-AUTHENTICATION-MIB
The Authentication User table. Remote dial-in clients can be
authenticated: locally using an internal database, or externally
using a Radius server server. Clients are defined internally
in this table. This table can have a special '
that defines the default user authentication method and
default client group name. The table lookup is always done first.
If the client's name is not found a 'default' entry defines
an alternative authentication methanism. If the 'default' entry
is not defined, and the client is not found in the table, the
client is denied access to the network, i.e. IPsec security
associations will not be created. If the client's name is
found in the table, the xauthUserAuthenProtocol
defines which authenication mechanism is to be used.
Specific users CAN be excluded by specifying 'always reject'
in the authentication protocol. The 'default' user can be
set to 'always accept' to allow ALL undefined users to
be automatically authenticated.
For 'internal authentication', whether through a specific
entry, or the default entry, the requested password must
match the configured password. '
Remote client example:
xauthUserName = [email protected],
xauthUserPassword = abc,
xauthUserClientGroup = Engineering,
xauthUserAuthenProtocol = internalAuthentication.
Parsed from file XEDIA-AUTHENTICATION-MIB.mib
Module: XEDIA-AUTHENTICATION-MIB
Vendor: Xedia Corporation
Module: XEDIA-AUTHENTICATION-MIB
[Automatically extracted from oidview.com]
xAuthUserTable OBJECT-TYPE SYNTAX SEQUENCE OF XAuthUserEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The Authentication User table. Remote dial-in clients can be authenticated: locally using an internal database, or externally using a Radius server server. Clients are defined internally in this table. This table can have a special '
' entry that defines the default user authentication method and default tunnel name. The table lookup is always done first. If the client's name is not found a 'default' entry defines an alternative authentication methanism. If the 'default' entry is not defined, and the client is not found in the table, the client is denied access to the network, i.e. IPsec security associations will not be created. If the client's name is found in the table, the ipsecRemoteClientAuthenProtocol defines which authenication mechanism is to be used. Specific users CAN be excluded by specifying 'always reject' in the authentication protocol. The 'default' user can be set to 'always accept' to allow ALL undefined users to be automatically authenticated. For 'internal authentication', whether through a specific entry, or the default entry, the requested password must match the configured password. ' Remote client example: xauthUserName = [email protected], xauthUserPassword = abc, xauthUserTunnelName = Engineering, xauthUserAuthenProtocol = internalAuthentication." ::= { xAuthUsers 2 }
xAuthUserTable OBJECT-TYPE SYNTAX SEQUENCE OF XAuthUserEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The Authentication User table. Remote dial-in clients can be authenticated: locally using an internal database, or externally using a Radius server server. Clients are defined internally in this table. This table can have a special '
' entry that defines the default user authentication method and default client group name. The table lookup is always done first. If the client's name is not found a 'default' entry defines an alternative authentication methanism. If the 'default' entry is not defined, and the client is not found in the table, the client is denied access to the network, i.e. IPsec security associations will not be created. If the client's name is found in the table, the xauthUserAuthenProtocol defines which authenication mechanism is to be used. Specific users CAN be excluded by specifying 'always reject' in the authentication protocol. The 'default' user can be set to 'always accept' to allow ALL undefined users to be automatically authenticated. For 'internal authentication', whether through a specific entry, or the default entry, the requested password must match the configured password. ' Remote client example: xauthUserName = [email protected], xauthUserPassword = abc, xauthUserClientGroup = Engineering, xauthUserAuthenProtocol = internalAuthentication." ::= { xAuthUsers 2 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.838.3.17.1.3.2.1 | xAuthUserEntry | 6 | 6 | An entry containing information applicable to a particular User. |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.838.3.17.1.3.1 | xAuthUserStats | 1 | 2 | None |
| 1.3.6.1.4.1.838.3.17.1.3.3 | xAuthUserActgTable | 1 | 13 | None |