• Home
• com.github.gun88
• fitnesse-radius-fixture
• 1.0.1
• source code
• EndpointDefinition.wiki

×

Project download

Many resources are needed to download a project. Please understand that we have to compensate our server costs. Thank you in advance.
Project price only 1 $

You can buy this project and download/modify it how often you want.

Resources.FitNesseRoot.PlugIns.RadiusFixture.UserGuide.GenericPacket.Table.EndpointDefinition.wiki Maven / Gradle / Ivy

---
Test
---
!***> definitions
!define REQUEST_0 { {{{Unknown (254), ID 0
NAS-Identifier: foo.bar.org}}} }

!define REQUEST_1 { {{{Unknown (254), ID 0
NAS-Identifier: foo.bar.org
Filter-Id: fooBar}}} }
*!
!2 Set Endpoint in RADIUS Fixture Table Mode
Host, Port and Shared Secret are the minimum set of coordinates to set a RADIUS endpoint and can be defined as shown in the following examples.

!3 Column Definition
Each endpoint coordinate has a dedicated column.

|ddt           :radius client fixture                                                                              |
|host          |generic port          |shared secret          |packet type|NAS-Identifier|request?    |response?   |
|${RADIUS_HOST}|${RADIUS_GENERIC_PORT}|${RADIUS_SHARED_SECRET}|254        |foo.bar.org   |${REQUEST_0}|${REQUEST_0}|

Also optional endpoint parameters can be defined in columns.

|ddt           :radius client fixture                                                                                                       |
|host          |generic port          |shared secret          |socket timeout|max retry|packet type|NAS-Identifier|request?    |response?   |
|${RADIUS_HOST}|${RADIUS_GENERIC_PORT}|${RADIUS_SHARED_SECRET}|4000          |4        |254        |foo.bar.org   |${REQUEST_0}|${REQUEST_0}|

!3 Inline Header Definition
Table header accepts endpoint coordinates in the following order: ''hostname'', ''port'', ''shared secret''.

|ddt        :radius client fixture|${RADIUS_HOST}|${RADIUS_GENERIC_PORT}|${RADIUS_SHARED_SECRET}|
|packet type|NAS-Identifier       |Filter-Id     |request?              |response?              |
|254        |foo.bar.org          |fooBar        |${REQUEST_1}          |${REQUEST_1}           |

Only these three main coordinates can be defined in table header. Optional endpoint parameters can be defined as shown in the Colum Definition mode.

|ddt           :radius client fixture|${RADIUS_HOST}|${RADIUS_GENERIC_PORT}|${RADIUS_SHARED_SECRET}            |
|socket timeout|max retry            |packet type   |NAS-Identifier        |Filter-Id|request?    |response?   |
|4000          |4                    |254           |foo.bar.org           |fooBar   |${REQUEST_1}|${REQUEST_1}|

!3 Endpoint Map Definition
Table header accepts endpoint coordinates set via map. Endpoint related keys are the following:
 * host
 * sharedSecret
 * genericPort
 * socketTimeout
 * maxRetry

|ddt        :radius client fixture|!{host:${RADIUS_HOST}, genericPort:${RADIUS_GENERIC_PORT}, sharedSecret:${RADIUS_SHARED_SECRET}}|
|packet type|NAS-Identifier       |Filter-Id|request?    |response?                                                                |
|254        |foo.bar.org          |fooBar   |${REQUEST_1}|${REQUEST_1}                                                             |