Uploaded image for project: 'OpenAM'
  1. OpenAM
  2. OPENAM-18149

Wrong log file is used for SAML2 extensions log message

    XMLWordPrintable

    Details

    • Bug
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 7.1.0
    • None
    • SAML
    • Rank:
      1|i05cli:

      Description

      Bug description

      Log message for SAML2 components end up in wrong debug log file

      How to reproduce the issue

      1. Configure AM 7.1.0 as SAML SP
      2. Configure 'auto-federation'
      3. Set 'message' level logging
      4. Configure some other AM as SAML IdP
      5. Configure SAML 'trust'
      6. Perform SAML SP-initiated SSO flow
      Expected behaviour
      debug log message for the SAML extensions, i.e. AccountMapper should end up in Federation debug log
      
      Current behaviour
      debug log messages end up in 'amUpgrade' log file
      
      excerpt from AM 7.1.0 debug logs
      [~/AM-Deployments/am710/am/var/debug]$grep -B1 'Auto federation attribute is set to' *
      amUpgrade-c.s.i.s.p.DefaultLibrarySPAccountMapper: 2021-07-27 13:34:22,379: Thread[http-nio-8080-exec-4]: TransactionId[287352f6-fc1d-40fe-afd2-c958939969c1-2474]
      amUpgrade:DEBUG: DefaultLibrarySPAccountMapper.getAutoFedUser: Auto federation attribute is set to: LoginId
      

        Attachments

          Activity

            People

            Unassigned Unassigned
            bthalmayr Bernhard Thalmayr
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated: