Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: link to examples


The aacli is a very useful tool to test what data the running IDP would send for a given subject (replace SOME_USERID below with the login name the subject would enter during authentication) to a given SP. Not only does that help verifying your attribute resolver  and attribute filter configuration when you're making changes to either (or both), it can also be useful in debugging access problems someone experiences at a given SP as you can easily compare what data would go out for different subjects (e.g. in cases where access works vs. where it failsfor one person but fails for another) without needing the subjectsubjects' s cooperation in this issue (or access to their password).


Code Block
titleCan be done for whole months or even years -cul /opt/shibboleth-idp/logs/idp-audit.log.201812*
21 unique relying parties
15 unique userids
406 logins

Maybe try one of the structured output formats for easy post-processing, e.g. JSON:

Code Block
titleCan be done for whole months or even years
$ -j /opt/shibboleth-idp/logs/idp-audit.log.20200[1-6]*
  "stats": {
    "logins": 8327,
    "rps": 211,
    "users": 150
  "logins_per_rp": {
    "": 29,
    "": 163,
    "usw.": "usf."

For more see the built-in help ( --help) or the examples in the documentation.


Code Block
titleLog SAML Messages on DEBUG
$EDITOR /opt/shibboleth-idp/conf/logback.xml  # Set <logger name="PROTOCOL_MESSAGE" level="DEBUG"/> and save
/opt/shibboleth-idp/bin/ -id shibboleth.LoggingService