Skip to main content

How to monitor claims in Active Directory Federated Services

Active Directory Federated Services (AD FS) allows two organizations to work in a partnership while less administrative overhead.  A resource organization can choose to allow an external organizations users selective access to their internal resources without managing additional user objects. The account organization an have their users access someone else's resources utilizing their normal Active Directory accounts.

 

AD FS does not have a mechanism that allows the resource organization to monitor who has accessed their resources.  The below setup and PowerShell script will allow for this data to be collected and presented to the resource organization so they know who made an AD FS claim and when.

 

Logging Setup:

Open Active Directory Federated Services console from the Administrator Tools.

Right click Federation Service and select Properties.

Click the Troubleshooting tab.

Check Informational and make note of the location where the logs will be stored.

image

 

Below is a PowerShell function that you can add to your code or Dot Source it in and use it on its own.

 

<#
.
SYNOPSIS
Extract the users and time stamp information from
ADFS Logs.
.
DESCRIPTION
Extracts the user name (including UPN suffix) and the
date/time stamp from the Active Directory Federated
Services troubleshooting log. The trouble shooting logs
must be set to record at least "Informational" events
for this to work.

.
PARAMETER ExcelFile
The name of the file being tested
.
EXAMPLE
get-ADFSClaimes

User TimeStamp
---- ---------
{
Spencer@Contoso.com} {2011-07-16T00:17:10}
{
Adam@Contoso.com} {2011-07-16T00:22:42}
{
Adam@Contoso.com} {2011-07-16T00:24:37}
{
Arthur@Contoso.com} {2011-07-16T00:30:26}
{
Adam@Contoso.com} {2011-07-16T00:32:19}
{
Don@Contoso.com} {2011-07-17T16:18:05}
{
Adam@Contoso.com} {2011-07-17T16:28:43}

Extracts all the logs in the default ADFS log file folder and displays the
User and date/time stamps for each claim.
#>


Function Get-ADFSClaims
{


# Set the location where to find the AD FS
# Troubleshooting logs.
$ADFSLogs = "N:\Data\*.log"


# Load the list of logs.
$ADFSLogList = Get-Item -Path $ADFSLogs

# Create and object to hold the results.
$LogObject = @()

# Parse through each log file and extract the list
# of users who made claims.
ForEach ($Log in $ADFSLogList)
{
$Contents = Get-Content $Log
For ($x=0 ; $x -le $Contents.count; $x++)


{
$Result = $Contents[$x] -Match "\w*\@\w*.com"
If ($Result -eq $True)
{
$LObj = New-Object PSObject
$LObj | Add-Member NoteProperty -Name User -Value $Matches.values
$Result = $Contents[$x-3] -match "\w*\-\w*\-\w*\:\w*\:\w*"
If ($Result -eq $True)
{
$LObj | Add-Member NoteProperty -Name TimeStamp -Value $Matches.values
}
$LogObject += $LObj
}
}
}
Write-Output $LogObject
}

Comments

Popular posts from this blog

How to run GPResult on a remote client with PowerShell

In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.

Set up your Environment to utilize Invoke-GPUpdate

I’m sitting in O’Hare enjoying my 3 hour layover as I get ready to teach a Windows 10 class in Fort Wayne.  I’m actually prepping for my class in Fort Wayne in a few weeks, 10982 Supporting and Troubleshooting Windows 10.  This class is very much like the Windows 7 version that I used to teach so I decided to up the detail quite a bit.  In the GPO troubleshootin chapter, I’m including a demonstration on how to use PowerShell’s Invoke-GPUpdate.  I needed to make sure the environment is set up for me to be able to utilize this cmdlet.  If you read the Notes section on Invoke-GPUpdate’s help file, you will see there are three firwall rules that need to be in place:          Remote Scheduled Tasks Management (RPC)          Remote Scheduled Tasks Management (RPC-ERMAP)          Windows Management Instrumentation (WMI-IN) I decided to create a little PowerShell script to crea...

Where did a User’s Account Get Locked Out?

Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction.  The code below is correct.   My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...