{
"code": 401,
"message": "X-F5-Auth-Token does not exist.",
"referer": "136.27.25.250",
"restOperationId": 6955449,
"kind": ":resterrorresponse"
}
"msg": "Status code was 401 and not [200]: HTTP Error 401: F5 Authorization Required"
BIG-IQ token expires by default after 300sec
{
"code": 401,
"errorStack": [],
"kind": ":resterrorresponse",
"message": "Invalid registered claims.",
"referer": "172.18.7.186",
"restOperationId": 2002730
}
"msg": "Status code was 401 and not [200]: HTTP Error 401: Unauthorized",
@focrensh, I have tested on both BIG-IP and BIG-IQ, all good.
For BIG-IP, if the Run check tasks succeed, it will stop and continue. If the Run check fails on 401, it will try to renew re-authenticate and refresh the token up to 4 times. If the Run check fails on other errors than 401, it won't go in the loop.
FYI, to test the changes on BIG-IP, I have reduced the token to 300sec to see the behavior by adding the following lines in authentication.yaml (only for testing, not in the PR)
Fixes #30
BIG-IP token expires by default after 1200sec
BIG-IQ token expires by default after 300sec
@focrensh, I have tested on both BIG-IP and BIG-IQ, all good.
For BIG-IP, if the Run check tasks succeed, it will stop and continue. If the Run check fails on 401, it will try to renew re-authenticate and refresh the token up to 4 times. If the Run check fails on other errors than 401, it won't go in the loop.
FYI, to test the changes on BIG-IP, I have reduced the token to 300sec to see the behavior by adding the following lines in
authentication.yaml
(only for testing, not in the PR)