fix(connect): HAWNG-487 apply authentication throttling to connect login

[tadayosi]

https://issues.redhat.com/browse/HAWNG-487

[tadayosi]

@kariuwu @grgrzybek Can you please review this?

[hawtio-ci]

Test results

Run attempt: 1532
Detailed summary

NAME	TESTS	PASSED ✅	SKIPPED 💤	FAILED ❌	ERRORS 🚫	TIME 🕖
results-quarkus-node(18)-java(17)-firefox	67	64	3	0	0	377.527
results-quarkus-node(18)-java(21)-firefox	67	64	3	0	0	373.859
results-quarkus-node(20)-java(17)-firefox	67	64	3	0	0	373.743
results-quarkus-node(20)-java(21)-firefox	67	64	3	0	0	371.238
results-springboot-node(18)-java(17)-firefox	67	63	4	0	0	375.999
results-springboot-node(18)-java(21)-firefox	67	63	4	0	0	368.986
results-springboot-node(20)-java(17)-firefox	67	63	4	0	0	374.079
results-springboot-node(20)-java(21)-firefox	67	63	4	0	0	379.359

[grgrzybek]

Looks good - there are no changes required at hawtio/hawtio side, right?

[github-actions]

Test Results

  8 files  ±0    8 suites  ±0   49m 54s ⏱️ +3s
 66 tests ±0   64 ✅ ±0   2 💤 ±0  0 ❌ ±0 
536 runs  ±0  508 ✅ ±0  28 💤 ±0  0 ❌ ±0 

Results for commit 57a035d. ± Comparison against base commit 131a2c8.

[tadayosi]

@grgrzybek Thanks.

Looks good - there are no changes required at hawtio/hawtio side, right?

No, no changes required. It's based on the existing capability in hawtio/hawtio.

However, just FYI, if we would look into HAWNG-487 more seriously, ideally there can be a few more enhancements from hawtio/hawtio and jolokia sides, including:

• Enable throttling on Jolokia endpoint in a Quarkus application with Quarkus Security: https://github.com/hawtio/hawtio/tree/4.x/examples/quarkus
• Implement the same throttling mechanism even at Jolokia itself in JVM agent mode

Anyway, we should work on them after product GA if we do.