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

Unable to add external data store in AM (Policy | Application) when using TLS/SSL

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 6.5.0.1
    • Fix Version/s: 6.5.1, 7.0.0
    • Component/s: console
    • Labels:
    • Target Version/s:
    • Sprint:
      AM Sustaining Sprint 60
    • Story Points:
      5
    • Needs backport:
      No
    • Support Ticket IDs:
    • Needs QA verification:
      No
    • Functional tests:
      No
    • Are the reproduction steps defined?:
      Yes and I used the same an in the description

      Description

      Bug description

      Attempting to create a new Secondary Configuration for External Data Stores using SSL/TLS fails with 'Server Connection Closed' and a message indicating that SSL/TLS may be required, followed by 'Bad Request'.

      How to reproduce the issue

      1. Setup AM and DS as an external Data Store.
      2. Goto CONFIGURE>Global Services>External Data Stores>Secondary Configurations
      3. Click [Add a Secondary Configuration]
      4. Provide the same info you have for DS (./status --trustAll output)
      5. Click the Use SSL to Enable SSL.
      6. Click on Create.
      7. See the two error pop-ups displayed in the Browser/console
      8. Click on Cancel
      9. Click on the Secondary Configuration TAB!
      10. Find the DS you just created, edit, save and no issue.
      11. On the Realm Default, change one or both of the Data Stores to the one created.
      12. Add an application and see if it makes it into the Data Store.

      Here I'm using AM 6.5.0.1 with DS 6.0.0.0

      Expected behaviour
      External DS Created Successful without errors in the browser and works as expected thereafter.
      
      Current behaviour
      'Server Connection Closed' with message that indicates that SSL/TLS may be required.
      

      Work around

      None

      Other notes:  Have moved the baseDN mismatch error part of the original Jira described here to OPENAM-14471.

       

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                lawrence.yarham Lawrence Yarham
                Reporter:
                ashley.hale Ashley Hale
              • Votes:
                0 Vote for this issue
                Watchers:
                8 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: