You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am in a Kubernetes environment. PEPs are running as sidecar containers to the actual apps. So I definitely want to know whats going on and how I am able to manage it without killing the whole POD. Perhaps its also a bad idea to run PEP Proxy as a sidecar?
After quite a while know more and more PEPs show the following behaviour in their logfiles (the corresponding web sites/endpoints are not responsing):
2021-07-05T10:11:13.351 - INFO: IDM-Client - Checking token with IDM...
2021-07-05T10:11:13.387 - INFO: Root - Access-token OK. Redirecting to app...
Refused to set unsafe header "accept-encoding"
Refused to set unsafe header "te"
2021-07-05T10:11:13.390 - INFO: IDM-Client - Token in cache, checking timestamp...
2021-07-05T10:11:13.390 - INFO: IDM-Client - b45166432595c88e40a8403147b197b5a876a400
2021-07-05T10:11:13.391 - INFO: IDM-Client - Token in cache expired
2021-07-05T10:11:13.391 - INFO: IDM-Client - Checking token with IDM...
Refused to set unsafe header "accept-encoding"
2021-07-05T10:11:13.421 - INFO: Root - Access-token OK. Redirecting to app...
Refused to set unsafe header "te"
2021-07-05T10:11:13.629 - INFO: IDM-Client - Checking token with IDM...
2021-07-05T10:11:13.667 - ERROR: IDM-Client - Error in IDM communication "Invalid token: access token has expired"
2021-07-05T10:11:13.667 - ERROR: Root - Invalid token: access token has expired
2021-07-05T10:11:20.752 - INFO: IDM-Client - Token in cache, checking timestamp...
2021-07-05T10:11:20.752 - INFO: IDM-Client - b45166432595c88e40a8403147b197b5a876a400
2021-07-05T10:11:20.752 - INFO: IDM-Client - Token in cache expired
2021-07-05T10:11:20.752 - INFO: IDM-Client - Checking token with IDM...
2021-07-05T10:11:20.778 - INFO: Root - Access-token OK. Redirecting to app...
Refused to set unsafe header "accept-encoding"
Refused to set unsafe header "te"
2021-07-05T10:11:28.711 - INFO: IDM-Client - Checking token with IDM...
2021-07-05T10:11:28.740 - ERROR: IDM-Client - Error in IDM communication "Invalid token: access token has expired"
2021-07-05T10:11:28.740 - ERROR: Root - Invalid token: access token has expired
I understand, that this refers to the access token between PEP and IdM, which seems to expire after quite a while (?). If this is the case, how am I able to refresh this without killing the whole system and redeploy it again? Who is responsible for refreshing these tokens and which features are the running services providing to enable this?
The text was updated successfully, but these errors were encountered:
I am in a Kubernetes environment. PEPs are running as sidecar containers to the actual apps. So I definitely want to know whats going on and how I am able to manage it without killing the whole POD. Perhaps its also a bad idea to run PEP Proxy as a sidecar?
After quite a while know more and more PEPs show the following behaviour in their logfiles (the corresponding web sites/endpoints are not responsing):
I understand, that this refers to the access token between PEP and IdM, which seems to expire after quite a while (?). If this is the case, how am I able to refresh this without killing the whole system and redeploy it again? Who is responsible for refreshing these tokens and which features are the running services providing to enable this?
The text was updated successfully, but these errors were encountered: