Most Valued User JoergG Posted January 29, 2020 Most Valued User #1 Share Posted January 29, 2020 Hi @ All, I have a problem to Connect a Netphone Server via CDS Api. CDS Api 11.32 Server Netphone 11.52 Windows 2016R2 Connect from CDS API to Server via IpPbx Username/Password Libmanager init: libManager = new LibManager(); libManager.BaseProtocol = SProxyObject.BaseProtocol.TCP; libManager.Username = "AdminUser"; libManager.Password = "AdminPw"; libManager.WSBaseUrl = "127.0.0.1"; libManager.AuthenticationMode = SProxyObject.AuthenticationMode.UsernamePassword; Trace Output: 29 13:13:54.209 0004 Verb CDSMgr CDSManager.NewRessourcen New Libmanager 29 13:13:54.298 0004 Info CDSClient LibManager.Initialize() () 29 13:13:54.298 0004 Alws CDSClient LibManager.Initialize() IpPbxCDSClientLib: PV:11.32.0.32 FV:11.32.0.105 29 13:13:54.299 0004 Alws CDSClient LibManager.Initialize() IpPbxCDSSharedLib: PV:11.32.0.14 FV:11.32.0.69 29 13:13:54.299 0004 Alws CDSClient LibManager.Initialize() Platform: x86 29 13:13:54.299 0004 Alws CDSClient LibManager.Initialize() FileCache: C:\Windows\system32\config\systemprofile\AppData\Local\T-Com\ActiveCallsDataService.exe\FileCache 29 13:13:54.300 0004 Info CDSClient LibManager.Initialize() DefaultTcpPort: 9094 29 13:13:54.300 0004 Info CDSClient LibManager.Initialize() DefaultHttpPort: 8094 29 13:13:54.300 0004 Info CDSClient LibManager.Initialize() RequestTimeout: 7500 29 13:13:54.305 0004 Info CDSClient LibManager.Initialize() done 29 13:13:54.316 0004 Alws CDSClient LibManager.WSBaseUrl 127.0.0.1 29 13:13:54.404 0004 Warn CDSClient AdminFacade. SecurityNegotiationException: SOAP security negotiation failed. See inner exception for more details. ~ ~Server stack trace: ~ at System.ServiceModel.Security.IssuanceTokenProviderBase`1.DoNegotiation(TimeSpan timeout) ~ at System.ServiceModel.Security.SspiNegotiationTokenProvider.OnOpen(TimeSpan timeout) ~ at System.ServiceModel.Security.TlsnegoTokenProvider.OnOpen(TimeSpan timeout) ~ at System.ServiceModel.Security.WrapperSecurityCommunicationObject.OnOpen(TimeSpan timeout) ~ at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout) ~ at System.ServiceModel.Security.CommunicationObjectSecurityTokenProvider.Open(TimeSpan timeout) ~ at System.ServiceModel.Security.SymmetricSecurityProtocol.OnOpen(TimeSpan timeout) ~ at System.ServiceModel.Security.WrapperSecurityCommunicationObject.OnOpen(TimeSpan timeout) ~ at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout) ~ at System.ServiceModel.Channels.SecurityChannelFactory`1.ClientSecurityChannel`1.OnOpen(TimeSpan timeout) ~ at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout) ~ at System.ServiceModel.Security.SecuritySessionSecurityTokenProvider.DoOperation(SecuritySessionOperation operation, EndpointAddress target, Uri via, SecurityToken currentToken, TimeSpan timeout) ~ at System.ServiceModel.Security.SecuritySessionSecurityTokenProvider.GetTokenCore(TimeSpan timeout) ~ at System.IdentityModel.Selectors.SecurityTokenProvider.GetToken(TimeSpan timeout) ~ at System.ServiceModel.Security.SecuritySessionClientSettings`1.ClientSecuritySessionChannel.OnOpen(TimeSpan timeout) ~ at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout) ~ at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout) ~ at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout) ~ ~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 System.ServiceModel.ICommunicationObject.Open(TimeSpan timeout) ~ at System.ServiceModel.ClientBase`1.System.ServiceModel.ICommunicationObject.Open(TimeSpan timeout) ~ at System.ServiceModel.ClientBase`1.Open() ~ at SWConfigDataClientLib.WCF.SWCFProxy`2.BeforeCall() ~ at SWConfigDataClientLib.WCF.SWCFProxy`2.CallContext..ctor(SWCFProxy`2 cCDSProxy) ~ at SWConfigDataClientLib.WCF.SWCFProxy`2.GetCallContext() ~ at SWConfigDataClientLib.Proxies.Admin.AdminFacade.GetUserAdminView1(Int32 GroupID, Boolean ShowUserFileSize, UserDeviceSmallMap& deviceMap) ~InnerException: Win32Exception Message The client and server cannot communicate, because they do not possess a common algorithm ~ at System.IdentityModel.SspiWrapper.AcquireCredentialsHandle(String package, CredentialUse intent, SecureCredential scc) ~ at System.ServiceModel.Security.TlsSspiNegotiation.AcquireDummyCredentials() ~ at System.ServiceModel.Security.TlsSspiNegotiation..ctor(String destination, Boolean isServer, SchProtocols protocolFlags, X509Certificate2 serverCertificate, X509Certificate2 clientCertificate, Boolean clientCertRequired) ~ at System.ServiceModel.Security.TlsnegoTokenProvider.CreateTlsSspiState(X509SecurityToken token) ~ at System.ServiceModel.Security.TlsnegoTokenProvider.CreateNegotiationState(EndpointAddress target, Uri via, TimeSpan timeout) ~ at System.ServiceModel.Security.IssuanceTokenProviderBase`1.DoNegotiation(TimeSpan timeout) 29 13:13:54.415 0004 Warn CDSClient AdminFacade.getException Exception will be interpreted as unspecified SSecurityAccessException 29 13:13:54.415 0004 Alws CDSClient LibManager.ResetPassword () Called after user name password authentification failed 29 13:13:54.418 0004 Warn CDSClient AdminFacade.getException SSecurityAccessException: Authentication failed: Username or password is incorrect. Can anyone help me ? Greetings Jörg Link to comment Share on other sites More sharing options...
Most Valued User JoergG Posted January 29, 2020 Author Most Valued User #2 Share Posted January 29, 2020 Hi @ All, After a lot of googling and testing on a laboratory server, maybe I found the cause. After I disabled TLS1.0 (server) in the registry, the problem occurred. RegKey: HKLM\SYSTEM\CurrentControlset\Control\SecurityProviders\SCHANNEL\Protokols\TLS 1.0\Server DisabledByDefault: DWORD=1 Enabled: DWORD=0 Original problem: Registration on a Netphone Client / SwyxIt with user / password works. The same user / password combination in the application (CDS-API) writes the above error. After activating TLS 1.0 (server) the registration works. best regarts Jörg Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now