More flexibility in the application of radius Rewrite

More flexibility in the application of radius Rewrite -

examples: Prefix bind a user name and remove domain prefix
radius Rewrite is a new feature in 10.5e To build. THUS Have yourself depict

many interesting Scenarien Two Simple application examples .:
1.The One two-factor login Have die Use names on the Radius server prefix
2 .Domäne "cut out" for entering the user name in syntax "domain username"
in my 1.Beipiel is a prefix "PL" insert.

The rewite policy / action

Add Rewrite action Radius_Request_Prefix
RADIUS.REQ.USER_NAME "RADIUS.NEW_AVP (1, " PL "+ RADIUS.REQ.USER_NAME) "

 replace  Add rewrite policy Radius_Request_Prefix RADIUS.IS_CLIENT Radius_Request_Prefix  

rewrite

  bind global Radius_Request_Prefix 100  

in 2.Example going to die domain "cut out" for entry of user names in the syntax domain username. This is possible with the following action:

Add

Rewrite action Radius_NoDomain RADIUS.REQ.USER_NAME
RADIUS.NEW_AVP (1 RADIUS.REQ.USER_NAME.AFTER_STR replace ( "\"))

In order to rewrite the request to the radius Sever, on must the radius request an email loadbalancer

radius Server hat die IP: 192.168.178.10

  Add service SRV_Radius  192.168.178.10  RADIUS 1812  

The LB VServer hat die 192 168 178 210

  Add lb vserver VS_Radius RADIUS 192 168 178 210 1812 -persistenceType NONE -cltTimeout 0  

  bind lb vserver VS_Radius SRV_Radius  

And radius action die is THUS:

 Add  authentication radius action Radius2AD -serverIP  192 168 178 210  -serverPort 1812   -radNASid CNS  

to note still did man /tmp/aaad.debug die circumscribes not looks, because only AFTER the VServer the radius request rewritten iS!

in DEM current build 10.5e (NS10.5: 54.008.e.nc) is building a vServers possible not binding. In eDocs is therefore described only global binding

Tweet