Last Modified: Sep 27, 2019
See more info
Known Affected Versions:
13.1.0, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 14.1.0, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 14.1.2, 184.108.40.206
Opened: Feb 28, 2018
The discover tasks is running periodically after user creates the task. But it may get stuck in the middle steps and fail to run periodically.
The discover task will periodically pull the OpenID information and update oauth jwt and jwk configurations in MCP. If the task sticks, the jwt and jwk configuration will not sync to the latest version and may cause access policy fail.
When HA failover group is set up and a discover task is created on one of the devices.
If the task is stuck in any step that is not SLEEP_AND_RUN_AGAIN for more than one minute, manually cancel and delete the task and create the same task again.
Discover task no longer gets stuck in CHECK_IS_ACTIVE step.