I could use some assistance understanding why I continue to receive “Uncaught TypeError: Failed to construct ‘URL’: Invalid URL” (Seen in the browser developer tools Console) when attempting to configure the Microsoft Sentinel Connector. I’ve read the documentation and following the instructions. We’re using Bitwarden (cloud-based). I’ve used the Client ID(client_id) and Client Secret (client_secret) provided under the Organization Info API Key dialog. I pasted the values and double checked the accuracy and clicking the Connect button in the Sentinel Connector Details doesn’t seem to do anything. After opening the Developer tools I am presented with the following:
react-dom.js:56 Uncaught TypeError: Failed to construct ‘URL’: Invalid URL
at OAuthButtonV2.js:224:38
at Object.n [as onClick] (OAuthButtonV2.js:244:26)
at o._onClick (index.js:1:165117)
at Object.vi (react-dom.js:202:330)
at ui (react-dom.js:32:27)
at xi (react-dom.js:32:81)
at zg (react-dom.js:55:403)
at rg (react-dom.js:56:317)
at react-dom.js:66:168
at react-dom.js:240:292
I have rotated the keys and tried with the same result. Is there a known issue or bug; or am I doing something incorrectly?
We’re seeing the same issue in sentinel when configuring the bitwarden data connector. All required fields validate, the “Connect” button turns blue, but clicking on it does nothing (no UI response at all).
In Edge with no extensions, dev tools shows:
”Uncaught TypeError: Failed to construct ‘URL’: Invalid URL”
We’ve checked the URLs (they’re the exact same provided by Bitwarden and presented in the field boxes on the connector configuration page), and they both appear fine with no extra characters or anything obvious.
Hi there, are you using the Bitwarden cloud or self-hosted?
Is there a trailing ‘/’
For self-hosted Bitwarden users, input your self-hosted URL. For example, https://<self-hosted-url>/identity . Be sure that the URL does not include any trailing forward slashes at the end of the URL "/ ".
Bitwarden cloud for us. Just tried it again since I haven’t worked on this since last week and it’s still giving us the Blue “clickable” button that does nothing.