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

OTP Email Sender node does not allow to specify connect timeout and IO/read timeout for underlying transport.

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 6.0.0, 6.0.0.1, 6.0.0.2, 6.0.0.3, 6.0.0.4, 6.0.0.5, 6.5.0, 6.0.0.6, 6.5.0.1, 6.0.0.7, 6.5.1, 6.5.0.2, 6.5.2, 6.5.2.1, 6.5.2.2, 6.5.2.3, 7.0.0, 6.5.3, 7.0.1
    • 6.5.4, 7.1.1, 7.0.3, 2021.8, 7.2.0
    • Azul OpenJDK "11.0.7" 2020-04-14 LTS
      DS 7.0.0 as AM configuration store, identity store, CTS persistence store
      Apache Tomcat 9.0.38
      AM 7.0.1
    • Rank:
      1|i036pv:ri
    • AM Sustaining Sprint 86, AM Sustaining Sprint 87
    • 3
    • Yes
    • No
    • Yes and I used the same an in the description, Yes but I used my own steps. (If so, please add them in a new comment)

    Description

      Bug description

      Every TCP-based communication should allow to set connect timeout and io/read timeout otherwise operating system defaults apply and typically they stem from 1970 where X.25 packet networks were used.

      How to reproduce the issue

      1. Setup simple SMTP server , e.g. Apache James on a host
      2. Configure Auth Tree with OTP Email sender node
        AM 7.0.1
      3. shut down interface of host with SMTP server
      4. Perform authentication using Auth Tree
      Expected behaviour
      auth node should fail after configurable timeout
      
      Current behaviour
      auth nodes waits until OS or JVM timeout happens.
      

      How would you set the OS or JVM TCP timeouts in FR Identity Cloud?

      Attachments

        Issue Links

          Activity

            People

              lawrence.yarham Lawrence Yarham
              bthalmayr Bernhard Thalmayr
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: