I programmed a programm in C# which accesses a web service with NTLM auth (Sharepoint 2010 server via SOAP). Now i want to port this programm to a Windows 8 app.
In my programm i used the following setting in my App.config to allow using the Windows login credentials:
<security mode="TransportCredentialOnly">
<transport clientCredentialType="Ntlm"/>
</security>
Since this isn't possible in a Windows 8 app, how can I still achieve this?
You need to code it manually. I've been able to connect to my SP using:
BasicHttpBinding MyHttpBinding = new BasicHttpBinding();
MyHttpBinding.Security.Mode = BasicHttpSecurityMode.Transport;
MyHttpBinding.Security.Transport.ClientCredentialType = HttpClientCredentialType.Ntlm;
Related
We're using a VB6 application on Windows 7+ machines (we can't upgrade it just yet). We call several web services in the application like so:
Set objClient = CreateObject("MSSOAP.SoapClient30")
objClient.MSSoapInit gszEmailWebServiceURL
objClient.ConnectorProperty("Timeout") = 30000
strXMLResponse = objClient.GetEmails()
Soon, all of the web services we call are changing to only allow TLS 1.2 connections.
Is there any way to set the object to use TLS 1.2?
I know that in .NET, you can do this:
System.Net.ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12
Is there something similar for VB6?
Also, I know that you can force the entire system to use TLS 1.2 by default, as specified here: https://support.microsoft.com/en-us/help/3140245/update-to-enable-tls-1-1-and-tls-1-2-as-a-default-secure-protocols-in. I tested this on one of our VMs and it indeed works, but we'd have to do this on every one of our client workstations (100+) that use this application, and so I'm hoping there is a way to do it from within the app itself, as we already have auto-update functionality for the app.
Thanks in advance.
I have terrible issue with Webtop 6.7 SP1 P12 (I have tried also testing P26) with SSO (kerberos) login into Webtop application.
On the user enviroment Web browser is in version IE 8.0.7601.17514 and operation system is Windows 7.
When I login into application (SSO authentication is succesful) result screen is missing some frame:
Sometimes frames are not behaving like this:
in this case URL is also strangely modified (part of it was deleted).
Java (1.6.0.27) is installed correctly. I also checked security setttings on JAVA and IE, but I don't see any incorrect parameters here.
When I use web browser Firefox 3.5.19 to login into the Webtop (SSO is active too) GUI is loaded correctly with frames..
My another test was under operation system Windows XP, IE 8.0.6001.18702. The Webtop GUI workiing correctly.
When I tried logging into Webtop instead of the hostname by use IP address application server, GUI working correctly. In this case SSO is off.
I tried change verzion JAVA vs IE but nothing helps.
Wireshark network protocol analyze capture this HTTP issue:
this problem occurs on 6 users of total 100.
Please, do you have any ideas for me?
Thank you so much.
Lukas
Investigating further we found that non-working users were part of 100+ AD groups resulting in a large kerberos token size.
I changed tomcat config file "server.xml" to increase http header limit to "maxHttpHeaderSize="16384"".
<Connector port="8080" maxHttpHeaderSize="16384" protocol="HTTP/1.1" ... />
Here is the link to fix:
http://blogs.adobe.com/livecycle/2012/08/avoiding-livecycle-kerberos-based-sso-problems-for-active-directory-users-with-large-group-memberships.html
Recently migrated an ASP.NET application from an old server to a new server
Both servers have the Same OS Windows Server 2008 R2 Standard
IIS 7.5 on both servers
SQL Server 2008 R2
The only difference is the amount of RAM and CPU speed
I have gone the server point to point and cannot find any differences.
I had a developer look at the code and he says its not the code
On the old server the website loads fine on the new server I get an error when browsing the website via domain name
Microsoft SQL Server Native Client 10.0 error '80040e4d'
Login failed for user 'NT AUTHORITY\IUSR'.
/lib/SQLHelper.asp, line 134
I cannot find anywhere that NT AUTHORITY\IUSR is being told to attempt to log in. Im thinking it is some kind of default. I have googled every line of the error trying to find a resolve and have been basically flipping switches to try to find an answer, nothing i have tried provides any good results.
Is there a setting in the deep dark belly of windows that im not checking?
'NT AUTHORITY\IUSR' is used by IIS as the account for anonymous users. This means that IIS is using passing through the authentication information to the SQL server rather than using a specified user account.
In most situations you would either have specified an account to be used in the connection string or disabled anonymous access to ensure that the account passed through is a authenticated user account.
It is possible to give the IUSR account permissions on the SQL Server.
Try looking at this article as it may give you some assistance The error "Login failed for user 'NT AUTHORITY\IUSR'" in ASP.NET and SQL Server 2008
This is Citrix technology based question. I need to develop windows app which should have functionality of remote session shadowing. We have server on which XenApp server and XenApp SDK is installed, and we get session information from it by using PowerShell. Problem is that XenApp SDK does not provide shadowing functionality. Basically i need something like client to client session shadowing.
Is this possible at all?
Thank You!
You can shadow a session remotely using WtsOpenServer and WtsStartRemoteControlSession api, just like rds/terminal server sessions. You MUST however shadow FROM an Ica (Citrix) session.
For OS < Vista you can use WinStationShadow.
See also: http://www.remkoweijnen.nl/blog/2007/10/30/new-terminal-server-apis-in-vista-sp1/
What is the best way to detect the current user Windows ID (on a corporate LAN on a Windows machine) in RIA?
I assume I should use WindowsAuth for this
In your web.config file, set the authentication mode to "Windows". Also, in your client (assuming you're using the Business Application Template), you'll need to set webContext.Authentication to a new instance of WindowsAuthentication in App.xaml.cs.