There really is no point in having this in the configuration, as in the real world it's highly doubtful one would never know what it is ahead of time. The suggested route (which is in place already) is to have the sessionId passed back-and-forth as a context property for later re-association.