-
Bug
-
Resolution: Done
-
Major
-
AD248 - RHJBEAP7.4-en-3-20240430
-
False
-
-
False
-
9
-
-
-
en-US (English)
-
AppDev Sprint May29 - Jun12
URL: | ch09s09 |
Reporter RHNID: | dcleave |
Section title: | Lab: Securing JBoss EAP |
Language: | English |
Issue description
bksecurity-ds as authentication method, datasource tests successfully, curl to 8080:messaging-client-secure/ fails which is correct as no uid/pw used, curl again with admin:admin fails. testing this in the browser brings up the login prompt but admin/admin also fails.
Attempted to use cmd to access DB but no tools installed to allow me to do this. Or any software.
I have spent time looking at what I had actioned up to this point and there is ZERO issues or mis configurations.
Controller accessed and data source test shows it connects successfully using bkadmin and redhat123 but when authenticating against admin with admin it fails.
I am aware that my colleague and other users have hit this exact same issue and was not able to resolve the issue.
Workaround:
Investigate why admin:admin credentials are failing despite successful data source tests with bkadmin and redhat123. Check permissions and configuration settings for bksecurity-ds, especially focusing on how it handles different user roles or credential sets.
Expected result: