Forms-Based Client-Initiated SSO - Some Basic Principals
I realise that there are already quite a number of questions on DevCentral relating to forms-based client-initiated SSO in APM, but I wondered if anyone could help me to understand some basic principals which would then assist me to find a solution to a problem I am having. I am attempting to perform SSO to an IBM Jazz Team Server (JTS) instance made available as an APM portal resource. JTS uses the Dojo toolkit to present a login form to users and overrides the standard 'submit' action with dojoAttachEvent. Obviously I don't expect a working solution for the above but in order to help me to work out it for myself I need to understand a few basic principals of how custom javascript is handled by the SSOv2 form handler. Are custom javascript replacements/amendments only injected into the page by APM once the form is identified or when the login criteria is matched? Is form identification performed once the page has fully loaded and the DOM is ready or prior to that point? Understanding at which point APM attempts form identification and whether it is a pre-requisite for using custom javascript would be really helpful. Many thanks.