Quote:
|
Could someone summarize and explain the more detailed aspects of the Robot Testing and Failed Client Authentication Testing? Specifically, what intentional interference actually happened, how did it cause problems, and what are they planning to do to fix the issue?
|
To add to what Al suggested, if you don't understand something in the report, this forum is a great place to ask for further explanation. The above is a good example. It is nearly impossible for all items in the report to be understandable to all that read it.
Alan did a great job of answering the question, but I'll add that the FCA is not itself anything to be worried about. It could be due to a typo, a forgetful user, or an attempt at cracking the password. The access point with logging enabled may log the mac address of the FCA client.
As mentioned in a previous post, the FW bug means that teams who used encryption for build season, opened their programming laptop at the event and unknowingly attempted to connect to their own robot with their build-season password resulting in an FCA. This was investigated to determine if it contributed directly to issues on Einstein.
Greg McKaskle
Greg McKaskle