What inspired this wish list request? Using a number of JSL scripts, I slowly am automating more of them so they can run without me. New authentication in JMP 18+ makes this more difficult.
What is the improvement you would like to see? A way to authenticate/use/something JMP in a manner it can be called from a schedule and not be impacted (or be predicatably impacted?) by authentication failures.
Why is this idea important? More and more I have created JSL scripts that are pretty stand alone in what they are able to automate. As a result, I find myself scheduling these scripts to run using windows scheduler. However, I encounter failures for "no traceable reason" that generally have been related to JMPs desire to re-authenticate. That window halts operation until a user intervenes, which isn't very possible since the user isn't actually the one 'clicking buttons'
I use JMP on a mixture of my laptop as well as several networked desktops. Overall the authentication isn't an issue, and, in fact, has been a much better user experience for when you use multiple computers.
That being said, automated script running throws a wrench in the system since it's unclear when authentication will need to take place. This is also the case for use cases where cloud systems may be desirable (eg AWS EC2) since you can't automate that system if a user needs to authenticate.
I'm not sure if the windows scheduler / cloud system would have a similar solution, but I think it would be great if JMP could figure out a way to allow these kind of background uses.
Or a better start might be a timeout with some logging that a batch file or something could key into for better failure logging - "Process failed due to need to reauthenticate"