No. It is definitely not as easy as choosing predefined policy and policy binding. What is publicly documented is only WS-Security (e.g UsernameToken).
However, what might be relatively easy (on modern BAW) is changing Target Environment to: Traditional or Container. Then you will lose support for Web Service Policy and also this legacy "Protected" checkbox - but you will have Basic Authentication enabled by default in the same way as in Cloud Pak. You don't have to do anything else. And it will work also on traditional WAS.
------------------------------
Sebastian Tylko
------------------------------
Original Message:
Sent: Mon October 27, 2025 05:48 PM
From: Manish Poddar
Subject: Protected Web Service
Thanks, Sebastian, for your quick response.
I believe the BPMHTTPBasicAuthentication policy set might be the most suitable option for us.

Do you have any documentation or examples related to WebSphere's BPMHTTPBasicAuthentication configuration?
------------------------------
Manish Poddar
------------------------------
Original Message:
Sent: Mon October 27, 2025 06:02 AM
From: Sebastian Tylko
Subject: Protected Web Service
This "protection" (checkbox: Protected) it is something very old and left for compatibility with archaic Lombardi versions.
Just uncheck this option for Web Service.
On BAW hosted on tWAS - use WebSphere Policy to enable basic authentication.
BAW from Cloud Pak for Business Automation has Web Services basic authentication enabled by default.
------------------------------
Sebastian Tylko