System.Web.Services.Protocols.SoapException: System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> Umbraco.Courier.Core.Exceptions.UnauthorizedClientException: User: [email protected] could not be authenticated at Umbraco.Courier.RepositoryProviders.WebserviceProvider.Security.SecurityHelper.ValidateUser(String login, String password) at Umbraco.Courier.RepositoryProviders.WebserviceProvider.Security.Authentication.AuthorizeByCredentials(String login, String password, Boolean cacheAuthResult) at Umbraco.Courier.RepositoryProviders.Webservices.Repository.AuthorizeAndLog(String memberName) at Umbraco.Courier.RepositoryProviders.Webservices.Repository.GetAvailableRevisions(String username, String password)
--- End of inner exception stack trace --- at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at Umbraco.Courier.RepositoryProviders.WebServiceProvider.RepositoryWebservice.GetAvailableRevisions() at Umbraco.Courier.RepositoryProviders.CourierWebserviceRepositoryProvider.GetAvailableRevisions() at Umbraco.Courier.UI.Pages.editRepository.OnInit(EventArgs e) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
Am running with v 7.12.1 and did set the useLegacyEncoding to true but still cant deploy anything. the weird this is that error just happened out of no where as we have successful deployment yesterday.
Finally got this working. Seems like the password in the DB was not the same on all environment even thought it has been updated with same in the back-end of umbraco.
UnauthorizedClientException with courier
Hi Guys,
Can anyone of you help with this
Am running with v 7.12.1 and did set the useLegacyEncoding to true but still cant deploy anything. the weird this is that error just happened out of no where as we have successful deployment yesterday.
Any help please
Anyone ??
Finally got this working. Seems like the password in the DB was not the same on all environment even thought it has been updated with same in the back-end of umbraco.
is working on a reply...