All Downloads are FREE. Search and download functionalities are using the official Maven repository.

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

The newest version!
---
Test
---
!***> definitions
!define REQUEST { {{{Unknown (254), ID 0
NAS-Identifier: foo.bar.org
Framed-Protocol: PPP}}} }
*!
!2 Set Endpoint in RADIUS Fixture Script 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.
The Scenario Table definition mode is the suggested  one.

!3 Row Definition
Each endpoint coordinate has a dedicated row.

|script               |radius client fixture                 |
|set host             |${RADIUS_HOST}                        |
|set generic port     |${RADIUS_GENERIC_PORT}                |
|set shared secret    |${RADIUS_SHARED_SECRET}               |
|set packet type      |254                                   |
|set request attribute|NAS-Identifier |with value|foo.bar.org|
|set request attribute|Framed-Protocol|with value|PPP        |
|check                |send packet    |Unknown (254)         |
|check                |request        |${REQUEST}            |
|check                |response       |${REQUEST}            |

Also optional endpoint parameters can be defined in rows.

|script               |radius client fixture                 |
|set host             |${RADIUS_HOST}                        |
|set generic port     |${RADIUS_GENERIC_PORT}                |
|set shared secret    |${RADIUS_SHARED_SECRET}               |
|set socket timeout   |4000                                  |
|set max retry        |4                                     |
|set packet type      |254                                   |
|set request attribute|NAS-Identifier |with value|foo.bar.org|
|set request attribute|Framed-Protocol|with value|PPP        |
|check                |send packet    |Unknown (254)         |
|check                |request        |${REQUEST}            |
|check                |response       |${REQUEST}            |

!3 Scenario Definition
RADIUS endpoint can be defined grouping coordinates rows in ''Scenario Table''.
|scenario         |my radius generic packet endpoint|
|set host         |${RADIUS_HOST}                   |
|set generic port |${RADIUS_GENERIC_PORT}           |
|set shared secret|${RADIUS_SHARED_SECRET}          |
|set packet type  |254                              |

|script               |radius client fixture                 |
|my radius generic packet endpoint                           |
|set request attribute|NAS-Identifier |with value|foo.bar.org|
|set request attribute|Framed-Protocol|with value|PPP        |
|check                |send packet    |Unknown (254)         |
|check                |request        |${REQUEST}            |
|check                |response       |${REQUEST}            |

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

|script               |radius client fixture|${RADIUS_HOST}|${RADIUS_GENERIC_PORT}|${RADIUS_SHARED_SECRET}|
|set packet type      |254                                                                                |
|set request attribute|NAS-Identifier       |with value    |foo.bar.org                                   |
|set request attribute|Framed-Protocol      |with value    |PPP                                           |
|check                |send packet          |Unknown (254)                                                |
|check                |request              |${REQUEST}                                                   |
|check                |response             |${REQUEST}                                                   |

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

|script               |radius client fixture|${RADIUS_HOST}|${RADIUS_GENERIC_PORT}|${RADIUS_SHARED_SECRET}|
|set socket timeout   |4000                                                                               |
|set max retry        |4                                                                                  |
|set packet type      |254                                                                                |
|set request attribute|NAS-Identifier       |with value    |foo.bar.org                                   |
|set request attribute|Framed-Protocol      |with value    |PPP                                           |
|check                |send packet          |Unknown (254)                                                |
|check                |request              |${REQUEST}                                                   |
|check                |response             |${REQUEST}                                                   |

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

|script               |radius client fixture|!{host:${RADIUS_HOST}, genericPort:${RADIUS_GENERIC_PORT}, sharedSecret:${RADIUS_SHARED_SECRET}}|
|set packet type      |254                                                                                                                   |
|set request attribute|NAS-Identifier       |with value|foo.bar.org                                                                          |
|set request attribute|Framed-Protocol      |with value|PPP                                                                                  |
|check                |send packet          |Unknown (254)                                                                                   |
|check                |request              |${REQUEST}                                                                                      |
|check                |response             |${REQUEST}                                                                                      |




© 2015 - 2025 Weber Informatics LLC | Privacy Policy