Resources.FitNesseRoot.PlugIns.RadiusFixture.UserGuide.Authentication.Script.EndpointDefinition.wiki Maven / Gradle / Ivy
The newest version!
---
Test
---
!***> definitions
!define REQUEST { {{{Access-Request, ID 0
User-Name: anon
Framed-Protocol: PPP}}} }
!define RESPONSE { {{{Access-Accept, ID 0}}} }
*!
!2 Set Endpoint in RADIUS Authentication 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 auth port |${RADIUS_AUTH_PORT} |
|set shared secret |${RADIUS_SHARED_SECRET} |
|set request attribute|User-Name |with value|anon|
|set request attribute|Framed-Protocol |with value|PPP |
|check |send authentication|Access-Accept |
|check |request |${REQUEST} |
|check |response |${RESPONSE} |
Also optional endpoint parameters can be defined in rows.
|script |radius client fixture |
|set host |${RADIUS_HOST} |
|set auth port |${RADIUS_AUTH_PORT} |
|set shared secret |${RADIUS_SHARED_SECRET} |
|set socket timeout |4000 |
|set max retry |4 |
|set request attribute|User-Name |with value|anon|
|set request attribute|Framed-Protocol |with value|PPP |
|check |send authentication|Access-Accept |
|check |request |${REQUEST} |
|check |response |${RESPONSE} |
!3 Scenario Definition
RADIUS endpoint can be defined grouping coordinates rows in ''Scenario Table''.
|scenario |my radius auth endpoint|
|set host |${RADIUS_HOST} |
|set auth port |${RADIUS_AUTH_PORT} |
|set shared secret|${RADIUS_SHARED_SECRET}|
|script |radius client fixture |
|my radius auth endpoint |
|set request attribute|User-Name |with value|anon|
|set request attribute|Framed-Protocol |with value|PPP |
|check |send authentication|Access-Accept |
|check |request |${REQUEST} |
|check |response |${RESPONSE} |
!3 Inline Header Definition
Table header accepts endpoint coordinates in the following order: ''hostname'', ''port'', ''shared secret''.
|script |radius client fixture|${RADIUS_HOST}|${RADIUS_AUTH_PORT}|${RADIUS_SHARED_SECRET}|
|set request attribute|User-Name |with value |anon |
|set request attribute|Framed-Protocol |with value |PPP |
|check |send authentication |Access-Accept |
|check |request |${REQUEST} |
|check |response |${RESPONSE} |
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_AUTH_PORT}|${RADIUS_SHARED_SECRET}|
|set socket timeout |4000 |
|set max retry |4 |
|set request attribute|User-Name |with value |anon |
|set request attribute|Framed-Protocol |with value |PPP |
|check |send authentication |Access-Accept |
|check |request |${REQUEST} |
|check |response |${RESPONSE} |
!3 Endpoint Map Definition
Table header accepts endpoint coordinates set via map. Endpoint related keys are the following:
* host
* sharedSecret
* authPort
* socketTimeout
* maxRetry
|script |radius client fixture|!{host:${RADIUS_HOST}, authPort:${RADIUS_AUTH_PORT}, sharedSecret:${RADIUS_SHARED_SECRET}}|
|set request attribute|User-Name |with value|anon |
|set request attribute|Framed-Protocol |with value|PPP |
|check |send authentication |Access-Accept |
|check |request |${REQUEST} |
|check |response |${RESPONSE} |
© 2015 - 2025 Weber Informatics LLC | Privacy Policy