I'd like you help to understand if it's possible to authenticate uSync calls with a basic authentication (HTTP 401 challenge).
Our costumer foced us to have the staging environment protected by a basic authentication (HTTP 401 challenge), and when I add the staging instance in the servers list of uSync publisher (on another instance, obv) it doesn't connect.
Connection error: "Unauthorized" 401 - Unauthorized: Access is denied due to invalid credentials.You do not have permission to view this directory or page using the credentials that you supplied.
Is there a way to bypass or authenticate the calls to the staging server?
if both servers are setup to use basic auth then these settings will be used. if the server you are sending from isn't then you can set a custom header in uSync's publisher settings to send the correct token.
uSync - Website with basic authentication enabled
Hi everyone!
I'd like you help to understand if it's possible to authenticate uSync calls with a basic authentication (HTTP 401 challenge).
Our costumer foced us to have the staging environment protected by a basic authentication (HTTP 401 challenge), and when I add the staging instance in the servers list of uSync publisher (on another instance, obv) it doesn't connect.
In the logs i have a warining during the call
it says
Is there a way to bypass or authenticate the calls to the staging server?
Umbraco 13.5.2 - uSync 13.1.7
Thank you so much
Hi,
If you are using Umbraco's Basic authentication setup then there is a way to bypass is.
if both servers are setup to use basic auth then these settings will be used. if the server you are sending from isn't then you can set a custom header in uSync's publisher settings to send the correct token.
e.g
if you have the whole site behind IIS / serve auth then you would need to exempt the /umbraco/uSyncReceive url from the basic auth for it to get past.
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.