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

Sample Facebook-ProvisionIDMAccount auth tree has wrong "connections"

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 6.0.0, 6.1.0
    • Fix Version/s: 6.0.0.1, 6.0.1, 6.1.0
    • Component/s: samples, trees
    • Labels:
      None
    • Needs backport:
      Yes
    • 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

      openam-samples/sample-trees/src/main/resources/root/AuthTree/Facebook-ProvisionIDMAccount.json has this content for the "ProvisionIdmAccountNode" entry:

            "da390917-3ea0-4e87-9bdf-d052cce36a54" : {
              "nodeType" : "ProvisionIdmAccountNode",
              "displayName" : "Provision IDM Account",
              "connections" : {
                "true" : "70e691a5-1e33-4ac3-a356-e7b6d60d92e0"
              }
            }
      

      Testing showed that this doesn't actually work. The auth tree dies following IDM registration, for reasons that are not at all clear (no error messages logged anywhere indicating why).

      How to reproduce the issue

      Use the sample auth tree to try to register with IDM, and try to have the tree continue to a successful session.

      Expected behaviour

      Login occurs following registration.

      Current behaviour

      Login fails with unhelpful error message and no useful log details.

      Code analysis

      The ProvisionIdmAccountNode extends SingleOutcomeNode; SingleOutcomeNode defines its one outcome as "outcome", not "true". When I change the sample to use "outcome", like so:

            "da390917-3ea0-4e87-9bdf-d052cce36a54" : {
              "nodeType" : "ProvisionIdmAccountNode",
              "displayName" : "Provision IDM Account",
              "connections" : {
                "outcome" : "70e691a5-1e33-4ac3-a356-e7b6d60d92e0"
              }
            }
      

      Then things work as expected.

        Attachments

          Activity

            People

            • Assignee:
              jake.feasel Jake Feasel
              Reporter:
              jake.feasel Jake Feasel
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: