siteadmin:clearpass_fticks
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| siteadmin:clearpass_fticks [2024/05/03 09:07] – admin | siteadmin:clearpass_fticks [2024/05/20 12:34] (current) – admin | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ======ClearPass FTICKS====== | + | ======ClearPass FTICKS |
| - | A prerequisite for FTICKS | + | **NOTE: This is untested.** |
| + | |||
| + | **This only applies | ||
| + | |||
| + | There are a number of steps required to set up FTICKS logging. | ||
| + | |||
| + | ====Syslog Targets==== | ||
| + | |||
| + | Create a new Syslog Target (**Administration**-> | ||
| + | |||
| + | {{: | ||
| + | |||
| + | ====Syslog Export Filter==== | ||
| + | |||
| + | Create a new Syslog Export Filter (**Administration**-> | ||
| + | |||
| + | {{:siteadmin:screenshot_2024-05-15_at_14.14.49.png? | ||
| + | |||
| + | where | ||
| + | * Export Template is //Session Logs// | ||
| + | * Export Event Format Type is // | ||
| + | * Local Facility Level is // | ||
| + | * Syslog Servers is the Jisc one created above | ||
| + | * and your ClearPass servers to generate logs from | ||
| + | |||
| + | Then in the //Filters and Columns// tab: | ||
| + | |||
| + | {{: | ||
| + | |||
| + | Ignore Option 1 and cut and paste the following into the Custom SQL box: | ||
| < | < | ||
| - | SELECT | + | SELECT |
| AS " | AS " | ||
| FROM public.tips_radius_session_log, | FROM public.tips_radius_session_log, | ||
| Line 18: | Line 47: | ||
| </ | </ | ||
| - | The line " | + | * Replace 0X000 with the Federation ID provided by Jisc. |
| + | |||
| + | * The line " | ||
| + | |||
| + | * The line "AND public.tips_radius_session_log.request_status = 1" ensures that only logs of successful authentications are pass on. | ||
| + | |||
| + | There might need to be other lines in there to ensure that the only logs sent to Jisc are ones that match a proxy between two sites specifically for govroam, rather than all proxied logs for non-govroam services. | ||
| + | |||
| + | =====SERIOUS LIMITATION===== | ||
| + | |||
| + | The big caveat with the above is that FTICKS logs will ONLY be generated where there is an Operator-Name variable set in the originating Access Request from the member site. No FTICKS if there isn't. Even if Clearpass inserts an Operator-Name, | ||
| + | |||
| + | **Thus as many as possible of your member sites need to configured their servers to set Operator-Name. This rules out any site using NPS as their ORPS unfortunately.** | ||
| + | |||
| + | ====Limitations on logging==== | ||
| + | |||
| + | Problem: Not all member organisations can or do set the Operater-Name attribute in their Requests. Ideally the RFO should be able to insert an O-N with a value set on behalf of your site but only some RADIUS servers are capable of doing this (FreeRADIUS, | ||
| + | |||
| + | When an RFO, scarfolk.gov.uk, | ||
| + | - If the Operator-Name is set to, say, 1arkham.nhs.uk then leave it as is. | ||
| + | - If the Operator-Name is missing the insert an Operator-Name with the value ' | ||
| + | - If there' | ||
| + | |||
| + | This way the home site will, at best, see an Operator-Name with the source site's value or, at worst, with it set to the Federation' | ||
| + | |||
| + | However, this conditional setting of Operator-Name isn't something found in servers like ClearPass, ISE or NPS. NPS is completely incapable of setting the Operator-Name. ClearPass can't do any sort of conditional setting. ISE might be able to. | ||
| + | |||
| + | With ClearPass you delete and add attributes to the Access Request but you can't conditionally replace or modify them. So the options are to either do nothing, which is what the configuration above does, and not try to add an Operator-Name where missing. Or, to add an Operator-Name with the default value of the RFO. Despite ClearPass allowing database access and has the ability to set and expand variables, there' | ||
| + | |||
| + | Overwriting the Operator-Name is an option but not a great one. Not only does it meant that sites which do set the Operator-Name will not be able to be identified outside of the Federation, but the FTICKS log won't be generated anyway. | ||
| + | |||
| - | The line "AND public.tips_radius_session_log.request_status = 1" ensures that only logs of successful authentications are pass on. | ||
| - | There might need to be othe lines in there to ensure that the only logs sent to Jisc are ones that match a proxy between two sites specifically for govroam, rather than all proxied logs for non-govroam services. | ||
siteadmin/clearpass_fticks.1714727264.txt.gz · Last modified: 2024/05/03 09:07 by admin
