If a user tries to authenticate with a token, you would see the authentication request in the Authentication Manager authentication activity log or the user event monitor if you use ID Plus.
Since we are in World Cup season, think of it this way: Authentication Manager is like a goalie in the World Cup. Every login request is a shot from a striker. Good requests score, but bad ones with the wrong username, bad PIN, or invalid token code get blocked before they hit the net. If the ball is never sent to the goal, the goalie just stands there with nothing to do.
If you are not seeing the request logged, then the server is not receiving the packets from the agent sending them. Start there with troubleshooting by running packet captures to see what's happeing.
Need more help about a specific error you might see? Please contact support to work directly with the support team to help you resolve the issue.
@Pole-identite (Customer) ,
If a user tries to authenticate with a token, you would see the authentication request in the Authentication Manager authentication activity log or the user event monitor if you use ID Plus.
Since we are in World Cup season, think of it this way: Authentication Manager is like a goalie in the World Cup. Every login request is a shot from a striker. Good requests score, but bad ones with the wrong username, bad PIN, or invalid token code get blocked before they hit the net. If the ball is never sent to the goal, the goalie just stands there with nothing to do.
If you are not seeing the request logged, then the server is not receiving the packets from the agent sending them. Start there with troubleshooting by running packet captures to see what's happeing.
Need more help about a specific error you might see? Please contact support to work directly with the support team to help you resolve the issue.