statusCheckInterval is too low

[alexandre-zia-ifood]

Hi,

I was wondering, why is statusCheckInterval too low?
The reason whay someone would use gluu-radius is to use twosetp authentication and take advantage of 2FA, this implies waiting for a human to take some action (approve or not on Supergluu) and no human could be that fast, and it doesn't matter if it took 1 second or two to detect step one auth success.
Shouldn't this be set to 1000 or 2000 ?

radius/Server/src/main/java/org/gluu/radius/server/filter/SuperGluuAccessRequestFilter.java

Line 21 in f2dffe3

private static final long statusCheckInterval = 50; // in ms

[uprightech]

Hello Alexandre ,
The statusCheckInterval is the interval between which the radius server will poll the Gluu server about 2FA authentication for the user. Too fast (too low a value) and you may poll the way too much , possibly impacting performance , too slow (higher value) and there will be a significant delay between when the user hits Approve on his phone and him getting authenticated.

That said , there is another value called the authenticationTimeout which is stored in Gluu server itself , and which you can set from the UI. That value is the value I think you're looking for.
Notice how from this loop it is used , and how the statusCheckInterval is used to "slow things down".

Hope the explanation helps.

It may be useful to know which specific issue you're having , if any,

Best Regards,
Rolain