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

logs indicate SNS comm failure are under CoreSystem log file, not the Push Log file.


    • Type: Bug
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: debug logging
    • Labels:
    • Sprint:
      AM Sustaining Sprint 32
    • Story Points:


      To reproduce

      1. Administrator creates an instance of the Push Notification Service
      2. Administrator creates an instance of the ForgeRock Authenticator (Push) module in the top-level realm and a ForgeRock Authenticator (Push) Registration module in the top-level realm,
      3. Administrator configures a registration chain on the top-level domain, including a DataStore module passing to the ForgeRock Authenticator (Push) Registration module,
      4. Administrator configures an authorisation chain on the top-level domain containing the ForgeRock Authenticator (Push) module
      5. Administrator goes to the push notification service and changes one of the configurations to be incorrect. Either:
        1. Access ID key
        2. Secret Access Key
        3. The SNS endpoint for the device being used in the test (APNS for iphone)
          Using the mobile device register with the authentication module as a demo user using the registration chain
      6. Logout
      7. Use the mobile device to authenticate with the auth chain
        Authentication should fail
      8. In the Debug logs there should be some indication of a failure to talk to sns.

      Expected Result
      Failure to communicate to the SNS during Authentication results in an error Entry in the Debug logs indicating that the SNS could not be contacted.

      Actual Result
      ERROR level logs are shown to indicate a failure to communicate with the SNS however they are logged under the Core System log file, not under the Push Log file.




            • Assignee:
              ken.stubbings Ken Stubbings
            • Votes:
              0 Vote for this issue
              3 Start watching this issue


              • Created: