Arkose: run() not reset() on repeat attempts to authenticate

[skooch]

Changes

Calling reset() instead of run() on the Arkose provider object breaks callbacks which prevents repeat authentication attempts with the same Auth0.js object. It now calls run() instead of reset().

Side note: As a customer, I found the JSDocs and Auth0 Docs rather lacking while trying to debug this issue. Parameters aren't present, just <optional> which is extraordinarily frustrating. There is also no information about behaviour, scope, or parameters in regards to triggerCaptcha().

Checklist

• I have read the Auth0 general contribution guidelines
• I have read the Auth0 Code of Conduct
• All tests and linters described in the Develop section run without errors

[skooch]

@srijonsaha Any chance of a review on this?

Dismissing this review, as I couldn't verify all the use-cases related to this change.

[skooch]

Thanks for responding @nandan-bhat, what use cases are missing from the tests?

[nandan-bhat]

Hello @skooch, Thanks for your patience. I am expecting @srijonsaha to review this PR.

[srijonsaha]

Hi @skooch could you list steps you took to reproduce your issue and anything specific about your setup? I was unable to reproduce it. Additionally, the reason for calling reset() here was to reset the Arkose challenge incase the Arkose object had already been initialized in a previous render but not call run(). run() should be called once triggerCaptcha() is fired by your event handler/hook following along with Arkose's API docs and should be the case for repeat authentication attempt as well.

https://developer.arkoselabs.com/docs/client-api#using-the-arkose-client-api