Get the wrong account on the application after two logon attempts
Hi Guys,
After a wrong log in with a bad password again the box AD Auth, I do a right log in with an other username and I get the account of the previous people on the backend.
Indeed, the authentication on the backend and the application is based on an HTTP Header built by the F5 from the information of session.ad.last.attr.UserPrincipalName get by an AD Query.
The mechanism:
I create a custom variable session after the logon page with session.logon.last.username@domain and I use this new custom variable to lookup in the AD with an AD Query after the AD Auth. I get the UserPrincipal Name to built the HTTP Header afterward.
Problem
I get the account of the previous people on the backend. It seems we have some caching during the APM Workflow when I change the account with a right password against the Ad Auth for the second attempt.
Do you why the APM Workflow keep my custom variable in cache ?
Thanks a lot for your help.
Morgan