<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: splunk and shibboleth log analysis in Monitoring Splunk</title>
    <link>https://community.splunk.com/t5/Monitoring-Splunk/splunk-and-shibboleth-log-analysis/m-p/155699#M7811</link>
    <description>&lt;P&gt;Lisa,&lt;/P&gt;

&lt;P&gt;Testing the Shibboleth log files on one of our Splunk DEV servers and when I go to add data (uploading via files from my computer) I’m not seeing the Sourcetype listed even though I added the following info into the following two conf files:&lt;/P&gt;

&lt;P&gt;• transforms.conf (/opt/splunk/etc/system/local/transforms.conf)&lt;/P&gt;

&lt;P&gt;[parse_idp_access]&lt;BR /&gt;
DELIMS = "|"&lt;BR /&gt;
FIELDS = requestTime, remoteHost, serverHost, serverPort, requestPath&lt;/P&gt;

&lt;P&gt;[parse_idp_audit]&lt;BR /&gt;
DELIMS = "|"&lt;BR /&gt;
FIELDS = auditEventTime, requestBinding, requestId, relyingPartyId, messageProfileId, assertingPartyId, responseBinding, responseId, principalName, authNMethod, releasedAttributeID, nameIdentifier, assertionID&lt;/P&gt;

&lt;P&gt;• props.conf (/opt/splunk/etc/system/local/props.conf)&lt;/P&gt;

&lt;P&gt;[idp_access]&lt;BR /&gt;
REPORT-parse_idp_access&lt;BR /&gt;
SHOULD_LINEMERGE = false&lt;/P&gt;

&lt;P&gt;[idp_audit]&lt;BR /&gt;
REPORT-parse_idp_audit&lt;BR /&gt;
SHOULD_LINEMERGE = false&lt;/P&gt;

&lt;P&gt;[idp_process]&lt;BR /&gt;
EXTRACT-idp_process1= (?TRACE|DEBUG|INFO|WARN|ERROR)\s[(?\S+?)]\s-\s*(?\S+?|(?\d{1,3}.\d{1,3}.\d{1,3}.\d{1,3})|(?\S+?)|(?.*)&lt;BR /&gt;
SHOULD_LINEMERGE = false&lt;/P&gt;

&lt;P&gt;Am I not using the right transforms/props conf files?&lt;/P&gt;

&lt;P&gt;Thx&lt;/P&gt;</description>
    <pubDate>Mon, 28 Sep 2020 20:13:51 GMT</pubDate>
    <dc:creator>jwalzerpitt</dc:creator>
    <dc:date>2020-09-28T20:13:51Z</dc:date>
    <item>
      <title>splunk and shibboleth log analysis</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/splunk-and-shibboleth-log-analysis/m-p/155695#M7807</link>
      <description>&lt;P&gt;Has anyone configured Splunk to read the audit logs from Shibboleth to try to summarize the source of the incoming authentication request?  The log format seems unique to Shibboleth .&lt;/P&gt;</description>
      <pubDate>Mon, 25 Nov 2013 19:19:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/splunk-and-shibboleth-log-analysis/m-p/155695#M7807</guid>
      <dc:creator>jimennis</dc:creator>
      <dc:date>2013-11-25T19:19:27Z</dc:date>
    </item>
    <item>
      <title>Re: splunk and shibboleth log analysis</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/splunk-and-shibboleth-log-analysis/m-p/155696#M7808</link>
      <description>&lt;P&gt;I have not, but it looks like this would be pretty simple. However, it does appear that the log files (especially the idp-process.log) can be configured, so you would probably have to tune this a bit. Also, the docs I read did not indicate that the log events would have a timestamp, which seems a curious omission. If you could edit your question to supply a few lines of the log files (sanitized of course), the community could be of more help.&lt;/P&gt;

&lt;P&gt;In &lt;CODE&gt;props.conf&lt;/CODE&gt; I would define some new sourcetypes as follows&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[idp_access]
REPORT-parse_idp_access
SHOULD_LINEMERGE = false

[idp_audit]
REPORT-parse_idp_audit
SHOULD_LINEMERGE = false

[idp_process]
EXTRACT-idp_process1= (?&amp;lt;loggingLevel&amp;gt;TRACE|DEBUG|INFO|WARN|ERROR)\s\[(?&amp;lt;errorCode&amp;gt;\S+?)\]\s-\s*(?&amp;lt;timestamp&amp;gt;\S+?\|(?&amp;lt;ip&amp;gt;\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3})\|(?&amp;lt;component&amp;gt;\S+?)\|(?&amp;lt;message&amp;gt;.*)
SHOULD_LINEMERGE = false
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;in &lt;CODE&gt;transforms.conf&lt;/CODE&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[parse_idp_access]
DELIMS = "|"
FIELDS = requestTime, remoteHost, serverHost, serverPort, requestPath

[parse_idp_audit]
DELIMS = "|"
FIELDS = auditEventTime, requestBinding, requestId, relyingPartyId, messageProfileId, assertingPartyId, responseBinding, responseId, principalName, authNMethod, releasedAttributeID, nameIdentifier, assertionID
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;If you use the sourcetypes in your &lt;CODE&gt;inputs.conf&lt;/CODE&gt;, you should have a start at this. Definitely needs some testing though.&lt;/P&gt;</description>
      <pubDate>Tue, 26 Nov 2013 04:22:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/splunk-and-shibboleth-log-analysis/m-p/155696#M7808</guid>
      <dc:creator>lguinn2</dc:creator>
      <dc:date>2013-11-26T04:22:42Z</dc:date>
    </item>
    <item>
      <title>Re: splunk and shibboleth log analysis</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/splunk-and-shibboleth-log-analysis/m-p/155697#M7809</link>
      <description>&lt;P&gt;Hello&lt;/P&gt;

&lt;P&gt;Thanks for the tip. I am working on getting a sanitized record for posting. Shibboleth uses the '|' character as it's field delimiter.  The first field is a timestamp field.  As soon as a colleague checks my sanitizing, I will post the record for reference.&lt;/P&gt;</description>
      <pubDate>Tue, 26 Nov 2013 14:47:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/splunk-and-shibboleth-log-analysis/m-p/155697#M7809</guid>
      <dc:creator>jimennis</dc:creator>
      <dc:date>2013-11-26T14:47:22Z</dc:date>
    </item>
    <item>
      <title>Re: splunk and shibboleth log analysis</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/splunk-and-shibboleth-log-analysis/m-p/155698#M7810</link>
      <description>&lt;P&gt;Here is sanitized record (all one line despite the line wrapping from the cut/paste):&lt;/P&gt;

&lt;P&gt;20131108T045952Z|urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect|_f2a07ca502e5e77114ee1e34e802145c|&lt;A href="https://my.xxx.xxx/shibboleth%7Curn:mace:shibboleth:2.0:profiles:saml2:sso%7Chttps://idp-xxxx.xx.xxxx.xxx/idp/shibboleth%7Curn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST%7C_4b2d89d047723cb9352de7b7901c2238%7Cuuuuuuuu%7Curn:oasis:names:tc:SAML:2.0:ac:classes:PasswordProtectedTransport%7Cuid,transientId,eppn,xxxPortalrol,%7C_9caa085551671cb968b0b616ad4ae848%7C%7C" target="_blank"&gt;https://my.xxx.xxx/shibboleth|urn:mace:shibboleth:2.0:profiles:saml2:sso|https://idp-xxxx.xx.xxxx.xxx/idp/shibboleth|urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST|_4b2d89d047723cb9352de7b7901c2238|uuuuuuuu|urn:oasis:names:tc:SAML:2.0:ac:classes:PasswordProtectedTransport|uid,transientId,eppn,xxxPortalrol,|_9caa085551671cb968b0b616ad4ae848||&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 15:22:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/splunk-and-shibboleth-log-analysis/m-p/155698#M7810</guid>
      <dc:creator>jimennis</dc:creator>
      <dc:date>2020-09-28T15:22:20Z</dc:date>
    </item>
    <item>
      <title>Re: splunk and shibboleth log analysis</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/splunk-and-shibboleth-log-analysis/m-p/155699#M7811</link>
      <description>&lt;P&gt;Lisa,&lt;/P&gt;

&lt;P&gt;Testing the Shibboleth log files on one of our Splunk DEV servers and when I go to add data (uploading via files from my computer) I’m not seeing the Sourcetype listed even though I added the following info into the following two conf files:&lt;/P&gt;

&lt;P&gt;• transforms.conf (/opt/splunk/etc/system/local/transforms.conf)&lt;/P&gt;

&lt;P&gt;[parse_idp_access]&lt;BR /&gt;
DELIMS = "|"&lt;BR /&gt;
FIELDS = requestTime, remoteHost, serverHost, serverPort, requestPath&lt;/P&gt;

&lt;P&gt;[parse_idp_audit]&lt;BR /&gt;
DELIMS = "|"&lt;BR /&gt;
FIELDS = auditEventTime, requestBinding, requestId, relyingPartyId, messageProfileId, assertingPartyId, responseBinding, responseId, principalName, authNMethod, releasedAttributeID, nameIdentifier, assertionID&lt;/P&gt;

&lt;P&gt;• props.conf (/opt/splunk/etc/system/local/props.conf)&lt;/P&gt;

&lt;P&gt;[idp_access]&lt;BR /&gt;
REPORT-parse_idp_access&lt;BR /&gt;
SHOULD_LINEMERGE = false&lt;/P&gt;

&lt;P&gt;[idp_audit]&lt;BR /&gt;
REPORT-parse_idp_audit&lt;BR /&gt;
SHOULD_LINEMERGE = false&lt;/P&gt;

&lt;P&gt;[idp_process]&lt;BR /&gt;
EXTRACT-idp_process1= (?TRACE|DEBUG|INFO|WARN|ERROR)\s[(?\S+?)]\s-\s*(?\S+?|(?\d{1,3}.\d{1,3}.\d{1,3}.\d{1,3})|(?\S+?)|(?.*)&lt;BR /&gt;
SHOULD_LINEMERGE = false&lt;/P&gt;

&lt;P&gt;Am I not using the right transforms/props conf files?&lt;/P&gt;

&lt;P&gt;Thx&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 20:13:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/splunk-and-shibboleth-log-analysis/m-p/155699#M7811</guid>
      <dc:creator>jwalzerpitt</dc:creator>
      <dc:date>2020-09-28T20:13:51Z</dc:date>
    </item>
    <item>
      <title>Re: splunk and shibboleth log analysis</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/splunk-and-shibboleth-log-analysis/m-p/155700#M7812</link>
      <description>&lt;P&gt;&lt;A href="https://wiki.shibboleth.net/confluence/display/IDP4/AuditLoggingConfiguration"&gt;link text&lt;/A&gt;&lt;BR /&gt;
The Shibboleth wiki page has information that will be useful in being able to parse the logs.&lt;/P&gt;

&lt;P&gt;Fields are extracted at various points through the life of a transaction so that adequate detail can be exposed about the request, the processing of the request, and the response. These extraction points are associated with collections of field extraction beans that do the actual work to pull data out of the state of the transaction and store it for output.&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;Built-In Fields&lt;/STRONG&gt;&lt;BR /&gt;
The fields that are supported out of the box are as follows (note that not every field is always populated, it depends on the timing of errors and the specific transaction being audited):&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;Generic Fields&lt;/STRONG&gt;&lt;BR /&gt;
 ST         Timestamp for start of flow&lt;BR /&gt;
 T          Timestamp event is recorded&lt;BR /&gt;
 e          WebFlow Event&lt;BR /&gt;
 URL    URL&lt;BR /&gt;
URI         URI&lt;BR /&gt;
DEST    Destination URL of outgoing msg&lt;BR /&gt;
s           IdP session ID&lt;BR /&gt;
AF           Authentication flow ID&lt;BR /&gt;
SSO        SSO flag&lt;BR /&gt;
a         Client address&lt;BR /&gt;
UA        User agent string&lt;BR /&gt;
P         Profile ID&lt;BR /&gt;
u         Username&lt;BR /&gt;
HASHEDu     Hashed username&lt;BR /&gt;
uu                Impersonating username&lt;BR /&gt;
attr                  Attribute(s)&lt;BR /&gt;
ROP              Requested authentication operator&lt;BR /&gt;
RPRIN        Requested authentication principals&lt;BR /&gt;
&lt;STRONG&gt;SAML Fields&lt;/STRONG&gt;&lt;BR /&gt;
SP  Service provider name&lt;BR /&gt;
IDP Identity provider name&lt;BR /&gt;
p   Protocol&lt;BR /&gt;
b   Inbound binding&lt;BR /&gt;
bb  Outbound binding&lt;BR /&gt;
n   NameID value&lt;BR /&gt;
f   NameID format&lt;BR /&gt;
SPQ NameID SPNameQualifier&lt;BR /&gt;
pf  NameIDPolicy required format&lt;BR /&gt;
PSPQ    NameIDPolicy required SPNameQualifier&lt;BR /&gt;
i   Assertion ID&lt;BR /&gt;
d   Assertion timestamp&lt;BR /&gt;
I   Inbound message ID&lt;BR /&gt;
D   Inbound message timestamp&lt;BR /&gt;
II  InResponseTo&lt;BR /&gt;
III Outbound message ID&lt;BR /&gt;
DD  Outbound message timestamp&lt;BR /&gt;
t   AuthenticationInstant&lt;BR /&gt;
x   SessionIndex&lt;BR /&gt;
ac  AuthenticationContext&lt;BR /&gt;
S   Status code&lt;BR /&gt;
SS  Sub-status code&lt;BR /&gt;
SM  Status message&lt;BR /&gt;
pasv    IsPassive&lt;BR /&gt;
fauth   ForceAuthn&lt;BR /&gt;
XX  Signed inbound messages&lt;BR /&gt;
X   Encrypted assertions&lt;BR /&gt;
XA  Encryption algorithm&lt;/P&gt;</description>
      <pubDate>Sat, 04 Apr 2020 13:15:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/splunk-and-shibboleth-log-analysis/m-p/155700#M7812</guid>
      <dc:creator>jsnyderlmco</dc:creator>
      <dc:date>2020-04-04T13:15:21Z</dc:date>
    </item>
    <item>
      <title>Re: splunk and shibboleth log analysis</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/splunk-and-shibboleth-log-analysis/m-p/155701#M7813</link>
      <description>&lt;P&gt;The link didn't come through. What wiki page? Maybe try to present the URL in a way that the site's algorithm won't block. (?)&lt;/P&gt;

&lt;P&gt;I'm not seeing any link to a wiki from app on Splunkbase, and I'm not seeing anything at github, except a shibb TA that is 4+ years old. (I.e., it appears not to be the one that is on splunkbase by SplunkWorks.)&lt;/P&gt;

&lt;P&gt;splunkbase.splunk.com/app/4389/&lt;/P&gt;</description>
      <pubDate>Sat, 04 Apr 2020 17:50:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/splunk-and-shibboleth-log-analysis/m-p/155701#M7813</guid>
      <dc:creator>wryanthomas</dc:creator>
      <dc:date>2020-04-04T17:50:41Z</dc:date>
    </item>
    <item>
      <title>Re: splunk and shibboleth log analysis</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/splunk-and-shibboleth-log-analysis/m-p/155702#M7814</link>
      <description>&lt;P&gt;&lt;A href="https://wiki.shibboleth.net/confluence/display/IDP4/AuditLoggingConfiguration"&gt;https://wiki.shibboleth.net/confluence/display/IDP4/AuditLoggingConfiguration&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 04 Apr 2020 18:10:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/splunk-and-shibboleth-log-analysis/m-p/155702#M7814</guid>
      <dc:creator>jsnyderlmco</dc:creator>
      <dc:date>2020-04-04T18:10:01Z</dc:date>
    </item>
  </channel>
</rss>

