I noticed that here we are using protectedId to select the credential while inside WFSLayerUtils is using sourceId, is this correct?

MapStore2/web/client/utils/WFSLayerUtils.js

Lines 65 to 95 in 0ec0d92

	export const needsCredentials = (options) => {
	const security = options?.security || {};
	const {type, sourceId} = security;
	const {username, password} = getCredentials(sourceId) ?? {};
	return type?.toLowerCase?.() === "basic" && (!username || !password);
	};
	export const getConfig = (options) => {
	const security = options?.security || {};
	const config = {};
	const {type, sourceId} = security;
	const credentials = getCredentials(sourceId);
	if (credentials) {
	const {username, password} = credentials;
	switch (type?.toLowerCase?.()) {
	case "basic":
	config.headers = {
	Authorization: `Basic ${btoa(`${username}:${password}`)}`
	};
	break;
	case "bearer":
	config.headers = {
	Authorization: `Bearer ${credentials.token}`
	};
	break;
	default:
	break;
	}
	}
	return config;
	};

I answer also here in order to explain the reasoning:
protectedId is for services data, and sourceId was a preexisting name used in layer.security object (for WFS mainly)
So in order to avoid confusion I have created two different names, but I can quickly replace them.

@MV88 If the credentials are still "basic", once set in the protected service pop-up, the service can no longer be saved.