Details

      Description

      From ScriptedDecisionNode.java:

      public class ScriptedDecisionNode implements Node {
      
          private static final String HEADERS_IDENTIFIER = "requestHeaders";
          private static final String EXISTING_SESSION = "existingSession";
          private static final String SHARED_STATE_IDENTIFIER = "sharedState";
          private static final String TRANSIENT_STATE_IDENTIFIER = "transientState";
          private static final String OUTCOME_IDENTIFIER = "outcome";
          private static final String ACTION_IDENTIFIER = "action";
          private static final String HTTP_CLIENT_IDENTIFIER = "httpClient";
          private static final String LOGGER_VARIABLE_NAME = "logger";
          private static final String REALM_IDENTIFIER = "realm";
          private static final String CALLBACKS_IDENTIFIER = "callbacks";
          private static final String QUERY_PARAMETER_IDENTIFIER = "requestParameters";
          private static final String ID_REPO_IDENTIFIER = "idRepository";
          private static final String AUDIT_ENTRY_DETAIL = "auditEntryDetail";
      

      Each of those are bindings available to scripted decision node scripts. The documentation under authentication-guide/scripting-api-node.html describes some of them with a bit of depth (e.g. requestHeaders, existingSession, sharedState, transientState, idRepository), some hardly at all (e.g. outcome, action, logger, callbacks) and some not at all (e.g. httpClient, realm, requestParameters, auditEntryDetail ).

      These bindings are critical for any meaningful scripted node development. Anyone without access to the AM source will know little to nothing about them, making custom node development extremely difficult.

      Every binding needs to be fully described, in terms of the full range of capabilities, features and expectations for them. Examples for how to use each of them should be included.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                chris.lee Chris Lee
                Reporter:
                jake.feasel Jake Feasel
              • Votes:
                0 Vote for this issue
                Watchers:
                7 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: