When I try to authorize account in a section Social Reach -> Settings -> Add Channel -> Twitter I always get blank page instead of Twitter login form and there is a message in the log about response403 Forbidden.
Message from the log file:
EPiServer.Social.Providers.OAuth.OAuthClient: OAuthClient: Cannot read response data System.Net.WebException: The remote server returned an error: (403) Forbidden. at System.Net.HttpWebRequest.GetResponse() at EPiServer.Social.Providers.OAuth.OAuthClient.GetWebResponseData(WebRequest webRequest) System.Net.WebException: The remote server returned an error: (403) Forbidden. at System.Net.HttpWebRequest.GetResponse() at EPiServer.Social.Providers.OAuth.OAuthClient.GetWebResponseData(WebRequest webRequest)
A URL of blank page is /EPiServer/EPiServer.Social/2.3.0/Providers/Twitter/TwitterLogin.aspx?redirect=1
It does not work with default creds after installation of package EPiServer.Social (consumerKey, consumerSecret).
Am I do something wrong or is it a bug in package EPiServer.Social (2.3.0)?
Hi Everybody,
When I try to authorize account in a section Social Reach -> Settings -> Add Channel -> Twitter I always get blank page instead of Twitter login form and there is a message in the log about response
403 Forbidden
.Message from the log file:
EPiServer.Social.Providers.OAuth.OAuthClient: OAuthClient: Cannot read response data
System.Net.WebException: The remote server returned an error: (403) Forbidden.
at System.Net.HttpWebRequest.GetResponse()
at EPiServer.Social.Providers.OAuth.OAuthClient.GetWebResponseData(WebRequest webRequest)
System.Net.WebException: The remote server returned an error: (403) Forbidden.
at System.Net.HttpWebRequest.GetResponse()
at EPiServer.Social.Providers.OAuth.OAuthClient.GetWebResponseData(WebRequest webRequest)
A URL of blank page is
/EPiServer/EPiServer.Social/2.3.0/Providers/Twitter/TwitterLogin.aspx?redirect=1
It does not work with default creds after installation of package EPiServer.Social (consumerKey, consumerSecret).
Am I do something wrong or is it a bug in package EPiServer.Social (2.3.0)?