in our company we use NT domain with NTLM. i have an asp login page for an app that will work in our intranet. but i couldn't find any resource for checking the username and password given in textboxes exists in domain or not.
View RepliesWorking on a new project and need IE to pass the LDAPUPN instead of NTLM. Anyone know of a way for to make this happen? Anyone know if this will change in IE in the near future? With the big push to go LDAP you would think this is an option.
View Replies View RelatedI am needing to query a .NET webservice from a classic ASP page. It works absolutely fine under anonymous authentication however I want to turn NTLM authentication on in order for me to ascertain the requesting user's context.
Detailed below is my code currently but it throws a very vague error when I turn on NTLM authentication. Code:
I am trying to read an XML file as below,
DS.ReadXml("http://localhost/PM/" & Me.ViewXML & ".XML", XmlReadMode.InferSchema)
Using Windows Authorization I get the exception below:
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Net.WebException: The remote server returned an error: (401) Unauthorized.
I have an asp page with just Integrated Windows authentication set. It works fine if it is accessed with just the server name, but it prompts the user to enter their credentials if it is accessed with the full domain name.
Any suggestions on how to eliminate the login box? ( Without allowing anonymous access...)
It's running on a W2K Server sp4 w/ IIS 5.
I'm working on an e-commerce website, using ASP and MS Access. The idea is that the user should register their FirstName, LastName, Email, Username and Password via an html form. This should be submitted to an ASP script which sends an auto responder email to the address submited in the form. The account should then be dumped in to the Access database, and the user should activate their account by clicking a link in the email.
I've got as far as sending the email when the user clicks the submit button on the form, but I'm very confused about how the link is sent in the email. I've been told that a random number generator should be used. I've been searching, but I can't find exactly what I'm looking for.
i want to implement authorization with windows authentication and don't
have the slightest clue of how to do this implementation. the basic
windows authentication for this .NET application is already setup. my
problem lies within my inability to manipulate the username captured in
the authentication process and my knowledge of how IIS is involved.
specifically, i have the following questions:
1) what object(s) can be used so that the user's username can be
manipulated for the authorization process?
2) in order to apply roles, do the users need to be placed in groups in
IIS? if so, how does this work?
3) is all the code that the application uses for roles in web.config?
or does global.asax play a role in this matter?
4) does the web.config file know to communicate with IIS because the
authorization type is set to windows?
5) once authorization is in place, can a section of an .aspx file be
visible to a group or can only entire files be secured for a group?
I am trying to integrate an application into our extranets.The extranet technology has its own authentication system requiring a domain user but uses anonymous authentication (from the perspective of IIS).I can get the username/password, but IIS is not aware of the user.
The application I am trying to integrate (to get the features I want) relies on either basic or NTLM authentication. The sites use SSL, so basic authentication is fine. Both applications live on the same server.I want to automatically authenticate the user in the second app. Any ideas?I have a few, but I don't know how to implement them.
One idea is to find a way to forward/redirect the basic authentication information to the secondary application. This would be easier (and less secure) if IE6 still supported the "http://user:pwd@server/" syntax.I could construct the authorization request-header myself on the server, but how would I convince browsers to send it?It should work with recent IE and NS browsers.
Anyone knows how to create the username/password authorization dialog in ASP?
View Replies View Related