Uploaded image for project: 'OpenAM'
  1. OpenAM
  2. OPENAM-759 Allow ClusterStateService to work with HTTPS endpoints
  3. OPENAM-760

Need to implement a better mechanism to check if OpenAM is up and running when endpoints are HTTPS

    XMLWordPrintable

    Details

    • Sub-task
    • Status: Closed
    • Minor
    • Resolution: Fixed
    • Express8, Snapshot9, Snapshot9.5, Snapshot9.5.1, Snapshot9.5.2_RC1, Snapshot9.5.2, 9.5.3_RC1
    • 10.0.0-EA
    • session
    • None
    • Rank:
      1|hzn7sf:

      Description

      If OpenAM is running behind a proxy such as apache then the container can be down; apache is still running and just checking if the socket is listening is not enough to validate if OpenAM is actually up and running. We implemented a fix that performs a simple GET request to the naming service and checks for HTTP 200. But if the OpenAM is running HTTPS then we the request is not processed correctly. We need to find a mechanism that (a) ensures the OpenAM is actually up and running when behind a proxy but each OpenAM ping is not doing a SSL negotiation as this will be very expensive. Perhaps look at a keep-alive SSL connection that can be reused.

        Attachments

          Activity

            People

            steve Steve Ferris
            steve Steve Ferris
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: