1. UNIFYNow Forum
  2. Bugs
0
Not a bug

Event Broker 3.2 check changes errors with Identity Broker 5.1 RC

Andrew Silcock 8 years ago • updated by anonymous 8 years ago • 4

I've upgraded IDB5.0.4 to 5.1 RC in the TAFE development environment and it now appears that the Event Broker 3.2 IDB Check Changes functionality no longer works.


Getting the following errors:


Operation faulted: The HTTP request is unauthorized with client authentication scheme 'Anonymous'. The authentication header received from the server was 'Negotiate'. - Please see the log viewer for more details.

An error occured when attempting to execute a function against the agent with the id 0c78b1fa-7b21-435c-b374-537221a38db4:
System.ServiceModel.Security.MessageSecurityException: The HTTP request is unauthorized with client authentication scheme 'Anonymous'. The authentication header received from the server was 'Negotiate'. ---> System.Net.WebException: The remote server returned an error: (401) Unauthorized.
at System.Net.HttpWebRequest.GetResponse()
at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
--- End of inner exception stack trace ---

Server stack trace:
at System.ServiceModel.Channels.HttpChannelUtilities.ValidateAuthentication(HttpWebRequest request, HttpWebResponse response, WebException responseException, HttpChannelFactory`1 factory)
at System.ServiceModel.Channels.HttpChannelUtilities.ValidateRequestReplyResponse(HttpWebRequest request, HttpWebResponse response, HttpChannelFactory`1 factory, WebException responseException, ChannelBinding channelBinding)
at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at IIdentityServiceCollector.GetAllAdapters(GetAllAdaptersRequest request)
at Unify.Product.EventBroker.IdentityBroker41Communicator.GetAllAdapters()
at Unify.Product.EventBroker.AgentRequestResponseEngine.IdBAgentGetAdapterNamesRequestAction(IAgent agent, XElement details, Guid agentId)
at Unify.Product.EventBroker.AgentRequestResponseEngine.ExecuteRequest(IAgent agent, XElement details, Guid agentId)
at Unify.Product.EventBroker.AgentEngineRepository.ExecuteAgainstAgent(Guid agentId, XElement details)
at Unify.Product.EventBroker.AgentEngine.ExecuteAgainstAgent(Guid agentId, XElement details)
at Unify.Product.EventBroker.AgentEngineLoggingDecorator.ExecuteAgainstAgent(Guid agentId, XElement details)

Answer

Answer
Curtis Lusmore 8 years ago

If that works, can you then try reverting the above change and then instead editing an element in %EB Install Directory%\Services\Unify.Service.Event.exe.config


Under configuration > system.serviceModel > bindings > basicHttpBinding > binding [name="IdentityBroker4Binding"]


change to the below

<security mode="TransportCredentialOnly">...</security>

and inside that

<transport clientCredentialType="Windows"/>
GOOD, I'M SATISFIED
Satisfaction mark
Satisfaction mark by Andrew Silcock 8 years ago
Under review
Curtis Lusmore 8 years ago

Hi Andrew,


As a temporary work around, can you try removing the following element from %IDB Install Directory%\Services\Unify.Service.Connect.exe.config


<security mode="TransportCredentialOnly"><transport clientCredentialType="Windows"/></security>

which is under configuration > system.serviceModel > bindings > basicHttpBinding > binding


Then restart the IDB service and let me know if the problem persists.

Answer
Curtis Lusmore 8 years ago

If that works, can you then try reverting the above change and then instead editing an element in %EB Install Directory%\Services\Unify.Service.Event.exe.config


Under configuration > system.serviceModel > bindings > basicHttpBinding > binding [name="IdentityBroker4Binding"]


change to the below

<security mode="TransportCredentialOnly">...</security>

and inside that

<transport clientCredentialType="Windows"/>
Andrew Silcock 8 years ago

Thanks Curtis that has fixed it, has opened up another issue but will raise that one separately.

Not a bug
Curtis Lusmore 8 years ago

I have tested this and can confirm that the change to Event Broker's Unify.Service.Event.exe.config mentioned in my previous comment is all that is required to resolve this issue - no changes to Identity Broker's Unify.Service.Connect.exe.config is required.

Customer support service by UserEcho