This topic contains 2 replies, has 2 voices, and was last updated by  AMDeveloper 3 weeks ago.

  • Author
  • #26135


    Is there any plan to have SAML-based Tree Nodes baked in the next version of product.

    Right now, it is kind of fragmented approach. As we know, we can accomplish SAML based use-case either through Integrated SAML Approach OR through Standalone approach

    Integrated SAML Approach does not look to fly as we are done with Modules and Chains (after the advent of Trees)

    Standalone approach is fine for now if it is silo and isolated work but truly speaking Tree based Nodes would be ideal.


     Andrew Potter 

    Not sure if it will be ‘baked in’, but there is a community node on the Marketplace you could use today:
    (Note that Readme states that this node needs v6.5.2 or above)


    Thanks Andrew. The node that you mention will work for us.

    Also I am seeking one general clarification across the nodes. There is one small paragraph at

    It basically tells us that
    In order to process responses to callbacks, it is necessary to know which callback is at which position in the list. You can find the position of the callbacks created by the current node by using the constant properties for each callback position in the processing node.
    If the callbacks were created in previous nodes, their positions must be stored in the shared state before subsequent nodes can use them.

    I am not fully getting where and how this constant properties for each callback is stored ?

    Would you please help me demystifying this aspect of callback in context of TREES


Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.

©2019 ForgeRock - we provide an identity and access platform to secure every online relationship for the enterprise market, educational sector and even entire countries. Click to view our privacy policy and terms of use.

Log in with your credentials

Forgot your details?