F5 APM Login Page Reload Attempts Username Evaluation

What you could do is create a macro.

Edit/rename the macro to loop 5 times

In the macro add your logon page and an empty agent (General purpose tab)

In the empty agent add the following :

expr { [mcget {session.logon.last.username} == ""]}

Name the branche "no username"

Change the no username ending to loop and the fallback to allow

Then add the macro instead of your current logon page, where the allow will be attached to your AAA agent (AD) and de loop ending to deny.

This will give the user 4 tries to find the find the right ccs.

Ones a username is entered and authentication fails the AAA agent will go directly to the logon page so the process of switching ccs files will fail in the same way as it did before.

Cheers,

Kees

No the cookie is inserted via the custom JavaScript code inserted into the login.inc page. The custom JavaScript applies a separate CSS file depending on whether the cookie is present. It also adds/removes the cookie based on clicking a link. First click adds cookie and reloads page, second click removes cookie and reloads page, third add/reload, etc. It transforms the link into a toggle for CSS files. The reload allows the different CSS file to be applied based on the presence of the cookie.

 

The best solution I could come up with is to create an empty policy object that looks at whether both username/password are blank and then have a custom ending that redirects back to the original URL to reset the process.

 

Hi,

 

How is the cookie inserted? Via an irule?

 

Cheers,

 

Kees

 

p.s.

 

It is default behaviour to post the password and username variable to the AAA agent when reloading the login page.