I am using some troubles getting the JUNOS Pulse client to play nicely with my Defender Tokens.
Now with my landing portal, there is no issue. You go to the landing page, type in LDAP credentials and get password on to the next page which asks for your token. You give it that and you are through and can access whatever you need.
However, the Pulse Client asks for a login and password-- then when it gets to the next token page, it always fails with the following log message:
Failed login for 'glaberge' from IP x.x.x.x because Next Token code is invalid.
But, again, we know it is not invalid because it works for the web portal. Anyone have any thoughts?
Could you verify that the time on both SA/MAG nodes( in case of Cluster) or the SA/MAG node is the same as on the RSA servers on the backend.
Sorry. I have been studying for a cerification and this fell to the wayside-- I did not open a ticket yet. I was planning on doing so if nothing panned out on the forums.
And I can try 4.0r7. I'll report back.
Unfortunately, neither of those worked so I am going to have to open a support ticket. Thanks for your time folks! I'll post the solution when I have it.