ADFS 3.0 - Implications of editing the onload.js file

hello.

i have seen couple of posts around internet changing sign in input validation adfs 3.0 allow users authenticate without needing supply domain associated account. works well. however, says on microsoft documentation making changes onload.js file change validation not supported. while work, implications of making such changes?

thank-you.

this forum active directory directory services.

you find assistance active directory federation services in msdn geneva forum: https://social.msdn.microsoft.com/forums/vstudio/en-us/home?forum=geneva.

regarding question, pretty said on same article. specific modification not supported:

• adding new ui widgets (buttons, input type=text, etc.)

• adding custom code events

• overriding user input validation

• inject ajax, jquery, etc.

and tells why:

• the same onload.js execute on adfs pages (ex. form-based logon page, home realm discovery page , etc.). need make sure code in script gets executed designed , not executed unexpectedly.

• when referencing html element, ensure check existence of element prior acting on element. provides robustness , ensures custom logic not executed on pages not contain element. can view html source on ad fs sign-in pages view existing elements.

do need more details on these?

---

note: posts provided “as is” without warranty of kind, either expressed or implied, including not limited implied warranties of merchantability and/or fitness particular purpose.

Windows Server  >  Directory Services