tag:support.arachni-scanner.com,2012-07-01:/discussions/suggestions/8419-provide-additional-documentation-when-dealing-with-authentication-requestArachni: Discussion 2018-05-04T08:38:14Ztag:support.arachni-scanner.com,2012-07-01:Comment/452192842018-05-04T08:38:12Z2018-05-04T08:38:12ZProvide Additional Documentation When Dealing With Authentication Request<div><p>Thing is that there's not more documentation to provide, once you're in a login script then you just use the Watir API to control the PhantomJS browser and interact with the webapp.</p>
<p>There could be bugs in Arachni if the script doesn't work or in Watir or maybe PhantomJS doesn't support the webapp for some reason (it's getting old, the new engine will have modern browsers), but there's really not much to document from my side.</p>
<p>To verify that your script is correct you can run it as a regular Ruby script that uses Watir and PhantomJS, completely outside Arachni; if it works, then the issue is with Arachni, if not then I can't do much about it.</p>
<p>Now, if you're unfamiliar with Ruby or Watir then that's way outside the scope of Arachni's documentation, you can educate yourself on those subjects as would anyone else that would like to use those tools.</p>
<p>Although, I guess I could add what I just wrote to the documentation to make things absolutely clear from the start, other than that though I don't see what else I can do.</p>
<p>Maybe also add a login script validation plugin that runs everything outside Arachni to make it easier to pinpoint where the issue lies?</p>
<p>Thoughts?</p></div>Tasos Laskos