I know this is a poor idea, but it is meerly a starting point for me.
How can I hardcode and pass the username / password information in an httpmodule (c#) for a windows based authentication app?
i want to get to a site where i would normally need to enter username
and password because authentication is set to windows, but i dont need
to enter it because a httpmod is automatically passing the credentials
along and i automatically get in.
View Complete Post
We have sharepoint 2010 foundation site that we can successfully login with via IE, Firefox, Chrome both on the domain and externally with Claims Authentication with only Windows Auth type selected (NTLM).
Once we add FBA and use the default signin page, we can still login (we select Windows Auth from the dropdown) BUT it only works on the domain. When we try to access externally, the only browser that works is FireFox. Both Chrome and IE just constantly redirect
back to the Choose Authentication dropdown screen.
We have tried for the last 2 days to sort this out. Has anyone else experience this? It looks like the default sign in page somehow doesn't set the cookie for IE and Chrome and just bounces us back to the sign in page...
Thanks for any info...
To clarify, we are not even using the FBA yet. We are trying to login only with the windows auth and domain accounts...
I have a MVC 2 application, that I setup with my SqlProfileProvider(setup with and already working with asp.net 2 apps) for user profile. I use Active Directory for my user makes with windows authentication but when I try to view the users profile setting I am getting "This property cannot be set for anonymous users." My question is Why? With MVC I call the command for
httpContext.Current.User.Identity.Name and I get my domain/user name. So I am not sure what step I am missing, is there something special i have to do for MVCX
I have WCF service being hosted in IIS with windows auth enabled, it is running under NetworkService account . I have a simple method on my WCF service which just reflects the identity of who is calling it.
I am using IIS to authenticate the user and pass me the WindowsPrincipal in the HTTP context.
I am consuming the WCF service witha client used in a WindowsService that is being run under the NetworkService account. When the WindowsService. When running b
Since upgrading some clients to SQL 2008 I am running into a problem with laptops that are members of a domain and using Windows Authentication while not connected to the domain.
The users are receiving errors:
The Local Security Authority cannot be contacted
Cannot generate SSPI context
I see many write ups on this in the SQL Forums and other places on the Internet.
My question is, is this a bug? If I use osql.exe as a test there is a distinct difference between SQL 2008 and SQL 2005.
I can use osql.exe from 90\tools\binn (SQL 2005) with the following command while not connected to the domain and it connects to either my SQL 2005 or 2008 instance.
osql -E -S <server>\<instance>
However, the exact same command using osql.exe from 100\tools\binn (SQL 2008) fails and generates the errors above.
My application is receiving the same error. It is using a DSN-less ODBC connection.
This is running XP SP3 and SQL 2008 Express SP1.
I'm trying to determine if this is a bug that may be fixed or if it is just life now and I need to adjust.