Govroam

The Roaming solution for the public sector

User Tools

Site Tools

You are here: start » siteadmin » fticks_for_ms_nps
siteadmin:fticks_for_ms_nps

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
siteadmin:fticks_for_ms_nps [2024/04/26 10:06] – adminsiteadmin:fticks_for_ms_nps [2024/05/20 08:53] (current) – admin
Line 4: Line 4:
  
 **This only applies to Federation Operators and not to individual sites** **This only applies to Federation Operators and not to individual sites**
 +
 +The syslog server configuration below is for NXLog which is only capable of sending us a form of the Windows Event logs, not FTICKS unfortunately. Recommendations for free Windows syslog servers start and stop with NXLog and, in it's Community from, is simply unable to generate FTICKS. 
 +
 +However, if you have existing software which can accept Windows Eventlogs (or otherwise access NPS logs) and change the format into FTICKS then feel free to do so. The criteria for FTICKS are:
 +
 +  * Uses the [[public:fticks|FTICKS]] format
 +  * Proxies to utilities.govroam.uk on port 514/UDP with Facility local5
 +  * Includes in the FTICKS '#FEDID=0X000#' where 0X000 is replaced by the Federation ID supplied by Jisc.
 +  * Filters down the proxied log to just those for
 +    * Users on the govroam SSID
 +    * Roams between member sites going through the ORPS
 +    * Successful authentications
 +    * Only authentications between member sites (i.e. NOT those to or from the Jisc NRPS, or within an organisation)
 +
  
 =====Installation===== =====Installation=====
Line 43: Line 57:
 <Output syslog_tls> <Output syslog_tls>
     Module      om_ssl     Module      om_ssl
-    Host        10.12.101.19+    Host        212.219.243.132
     Port        6514     Port        6514
 #   CAFile      c:/Program Files (x86)/nxlog/data/cacert.pem #   CAFile      c:/Program Files (x86)/nxlog/data/cacert.pem
Line 55: Line 69:
 <Output syslog_tcp> <Output syslog_tcp>
     Module      om_tcp     Module      om_tcp
-    Host        10.12.101.19+    Host        212.219.243.132
     Port        601     Port        601
     OutputType  Syslog_TLS     OutputType  Syslog_TLS
Line 73: Line 87:
     <Exec>     <Exec>
 # Don't send log if going to or coming from a NRPS # Don't send log if going to or coming from a NRPS
 +# Change to math the ClientName and ProxyPolicyName as appropriate
    if $ClientName =~ /NRPS/i drop();    if $ClientName =~ /NRPS/i drop();
    if $ProxyPolicyName =~ /NRPS/i drop();    if $ProxyPolicyName =~ /NRPS/i drop();
  
 # Replace with the provided Federation ID # Replace with the provided Federation ID
-   $FederationID = "000X0";+   $FederationID = "XXXXX";
  
 # Send Client Name as the Operator Name if present, otherwise use a default. # Send Client Name as the Operator Name if present, otherwise use a default.
Line 96: Line 111:
 </Route> </Route>
 </code> </code>
 +
 +Replace //XXXXX// with the Federation ID supplied by Jisc.
 +
 +Replace //1something.here// with your realm, prefixed by '1'.
 +
 +The Client Name and the Proxy Policy Name for receiving from/sending to the Jisc NRPS would have to contain 'NRPS' for the above to work. Otherwise change the above so that requests to/from the NRPS are excluded from the logging. 
  
 Save the file and restart the service. Save the file and restart the service.
 +
 +To make this work properly, the Client Name has to be in the form of a realm e.g. 1holby.nhs.uk for each of the Clients.
  
 The stanza, syslog_tls, is just there for information. It's not actually used in this configuration. At a later date we'll be looking at encryption but there's a PKI to build. The stanza, syslog_tls, is just there for information. It's not actually used in this configuration. At a later date we'll be looking at encryption but there's a PKI to build.
siteadmin/fticks_for_ms_nps.1714125961.txt.gz · Last modified: by admin