the base URL setting allows uSync to send messages to one URL (your aws url) while signing the message as if it is going to another (your firendly url).
So i think in your case you add the server with the aws URL and then set the base url to the friendly one and that should do it.
(if you are running v9 - you should be able to set the base url on the server setting page once you have added the server (see https://github.com/Jumoo/uSync.Complete.Issues/issues/147)
I set the value, but it doesn't seem to have changed the result, I still get unauthorized when I do "check access".
Is there something I could look for in the logs to try and understand whats wrong?
Another thing I've noticed: If we enable an http password (used to keep bots out of our staging environments), we also get unauthorized.
I tried passing user:password@rawurl but it doesn't help
if you turn on Trace logging for uSync (http://usync.jumoo.co.uk/docs/uSync/guides/debugging#verbose-logging) you should get a little bit more in terms of what is happening inside the authentication process.
often it is one of these three
1). the URL mismatch (hence the baseURL)
2). Additional authentication layers on the URL (e.g basic auth, etc)
3). some proxy/firewall interception re-writing of the messages.
uSync Publisher in AWS behind proxy shows wrong url for "Current Server :"
Hi,
I'm trying to set up uSync Publisher (free trial) on a site hosted in elastic beanstalk (on linux).
We use a proxy to provide a friendly url and https, the site is also available on http://[rawawsurl]
In the publisher setting page, I'm unable to add the server with https://[friendly]
https://[friendly]/umbraco#/settings/uSyncPublisher/
If I set Umbraco's WebRouting UrlProviderMode to Absolute it shows the current server as http://[friendly]
If I set Umbraco's WebRouting UrlProviderMode to Auto it shows the current server as http://[rawawsurl]
I can "Add new Server" using http://[rawawsurl]
I'm unable to "Add new Server" using https://[friendly]
Do you have any suggestions about how/what to configure to resolve the issue?
Thanks
Hi Andrew,
it sound like you need to set the base URL on the server.
http://usync.jumoo.co.uk/docs/8.x/complete/publisher/config#baseurl
the base URL setting allows uSync to send messages to one URL (your aws url) while signing the message as if it is going to another (your firendly url).
So i think in your case you add the server with the aws URL and then set the base url to the friendly one and that should do it. (if you are running v9 - you should be able to set the base url on the server setting page once you have added the server (see https://github.com/Jumoo/uSync.Complete.Issues/issues/147)
Thanks Kevin,
I set the value, but it doesn't seem to have changed the result, I still get unauthorized when I do "check access".
Is there something I could look for in the logs to try and understand whats wrong?
Another thing I've noticed: If we enable an http password (used to keep bots out of our staging environments), we also get unauthorized. I tried passing user:password@rawurl but it doesn't help
Hi Andrew,
if you turn on Trace logging for uSync (http://usync.jumoo.co.uk/docs/uSync/guides/debugging#verbose-logging) you should get a little bit more in terms of what is happening inside the authentication process.
often it is one of these three
1). the URL mismatch (hence the baseURL) 2). Additional authentication layers on the URL (e.g basic auth, etc) 3). some proxy/firewall interception re-writing of the messages.
if you are running 9.0.6 you can actually turn of the inclusion of the host name in the message signature https://github.com/Jumoo/uSync.Complete.Issues/issues/148 (needs to be done on both ends, or nothing works between them)
Thanks Kevin,
Setting "IncludeHost": false seems to have done the trick.
:D
FYI:
In http://usync.jumoo.co.uk/docs/uSync/guides/debugging/#verbose-logging
It says to use "uSync": "Trace" , but that gave me an error, "Debug" and "Verbose" seem to be ok.
is working on a reply...