I'm trying to get the NT login id of a user on a web page without making the
user type it into a login box. I'm using the LOGON_USER server variable.
The problem is, if the web page allows anonymous access, LOGON_USER returns
nothing. If the page is set to Basic Security, the NT login popup box comes
up, even though the user is already logged into the network, and HAS access
to this page.
Moreover, if I try this on my PC instead of our webserver, it
works like I would expect. That is, when set to Basic Security, it does NOT
pop up a login box if the user is allowed to view the page, and LOGON_USER
returns the userid. Is there some setting on the server I need to change?
Or something else?
I know that if you intend to use the LOGON_USER in an ASP page you need to have Windows Authentication selected.
I have a website in one domain which can be accessed by 2 other domains. If I am to change to Windows Authentication, will there be a security issue of any type?
I create a web site in a Windows 2003 server/IIS6, and I used asp pages to get ServerVariables. After I set FrontPage Extension 2002, some ServerVariables like LOGON_USER become null. Any body has an idea?
I have an intranet site hosted in IIS 5.0 Win2000, and want to display the name of the user logged into the local machines(WinXP) in the pages they access like 'Welcome JohniBravo'.
So, i used the Request.ServerVariables("LOGON_USER"), but get a blank ("") displayed in the page. And i even tried "REMOTE_USER" but, still the same. from somewhere i got to know that theres something called 'Allow anonymous user' should be enabled to get these info from servers. help me with the same?
I have used the same syntax in two pages and sometimes each server variable is return, and sometime it is blank. In fact, I created a test page this morning which worked fine, and then an hour later the variables are blank. I read some of the threads about the anonymous user box in IIS, but this just seems strange.
P.S. Each PC in our environment is authenticated through active directory (just to logon to the PC, not security applied to the web folders).
I'm using Windows Integrated Authentication on my company intranet ASP web site (IIS6 W2K3).
I would like to know how could I get the full Active Directory domain name from the Logon_User variable.
I always get the netbios name of the domain, but I need the full domain name to be able to distinguish users (because actually there is two companies on the intranet having their AD forest linked, but also having some subdomains with identical netbios name !).
I mean, for instance for a user login "theuser" coming from the domain is "thedomain.thecompany.com", I need to get in Logon_User environement variable the following content: "thedomain.thecompany.com heuser" At the moment I only get "thedomain heuser", excepted if I switch to basic authentication, that I don't want.
I have 2 webs under my default web running win2003
1. A front-page intranet 2. A asp (not .net) web is fine
Both allow anonomous access. My front page web always gets a BLANK Request.ServerVariables("Logon_User"). The asp web gets the logon_user OK. Both webs have a global.asa that has Code:
Request.servervariables("Logon_USer") is working perfectly well for one asp page returning the NT userid as expected but returning an empty string for another asp page.Both the asp pages are in the same directory.This directory have both Anonymous Access and Integrated Authentication enabled att IIS.
I'm trying to determine whose looking at various pages on our intranet and wanted to use
Request.ServerVariables("logon_user")
but it just gives me a blank value.
I'm thinking its got something to do with Authentification in IIS however when I turn Anonymous users off and use domain users instead it prompts me for a username and password when viewing the webpage ...
I have a non anonymous site in IIS5 The site is for collecting any kind of data from employees. Authentication is done with the server variable "Logon_User"
Pages:
start.asp - Authentification mask appears --> form.asp - form for data input --> form_ack.asp - displays the data again and stores in SQL when acknowledged in checkboxes
After data are stored I'd like to have a button such as "Log off" which points back to start.asp.
In the samples I tried there is always the current logged in user present even when I do a "session.abandon" or "Session.Contents.Remove"
IIS can handle security on its own without the need for complex scripting and i like the idea of being able to just let the system do it however im not sure how to set such things up and would that mean that if you used something like integrated windows authentication that security is delt with by windows and its users info rather than getting the info from a database of my choosing ?
the whole concept is quite confusing to me but there must be a simple ish way to set up at least some form of secure site area within my web.
I am starting to learn asp and I have IIS installed on my WIN xp pro machine. Do I have to worry about security for any reason at all. I don't believe I have file sharing on at all, then again, I don't know if that has anything to do with this.
How do I run security through all of the pages? The users log in, an asp checks their password, then what do I do to secure the pages from users that do not enter the password?
Developed a web application which adopts a custom security model which displays a login page and requests a username/password combination. The username works in a mixed-mode of usernames matched with the windows login name and some extra accounts (similar to SQL mixed-mode security). Web application is executed both in the corporate intranet and externally on the web. Getting user complaints about having to login to the web application when they have already logged-on to windows. I have coded a challenge/response (response.status=401) to get a user's window login through the ServerVariables. This seems to work OK for the intranet access. If the user's windows account is not located in the application database then I redirect to the standard login page for the username/password combination. When the application is executed across the internet through a firewall, the user is prompted by IE to enter the windows domain, username, and password. There seems to be no mechanism to avoid this because of the challenge/response code. I wish that with external access from the internet that users are automatically directed to the application login screen and not faced with the IE windows authentication dialog.
Does anyone know how to implement one way hashing or encryption using ASP 3.0 and no additional components.
I need to secure a intranet application which is being moved online, currently the passwords are stored in plain text, ideally id like to hash the passwords in the database and hash the form data when testing, but I don't seem to be able to find any hashing methods for standard ASP, perhaps someone has a nice code snippet for hashing.
is there a way to login to a particular security group from asp?I use IP addresses and email addresses to identify web users and most have general IWAM_COMPUTERNAME access. Once web users login is there a way to give SOME of them access to a NT security group based on stored NT user/password information?
I am working on a new feature on my website where people can write their own HTML files. They are actaully going to have .ASP extensions, and are hosted on my webserver. So, what security issues can you suggest? So far all I have got is disabling '<% %>' tags. Anything else?
I'm developing a local intranet site. i'm just new in ASP, could anyone help me how to put security?i have username and password but i want the site not to go back on the previous pages after logging off.
I'm using macromedia dreamweaver and VBscript, i have a database using MS Access.
i am developing a project thats gonna handle some transactions too.Since this is my first commercial project so i am worried about its security. so my question is "is asp safe enough to use with something serious ?" or i should use something else like PHP .
I'm about to embark on a project that will allow my clients to produce invoices via any internet enabled PC. This post is regarding the security options available to me.
I will implement a Username/Password scheme to restrict access to the facility, but since part of the facility will allow access to customer information I wondering if I should also look at a more secure protocol than simple HTTP.
I have very little knowledge regarding the options available to me and as such I'm hoping someone can give me some suggestions of an overview of the different things I could use.
One more conceptual thing! Tell me if i am right! I have developed a concept that SSL does three jobs!
1) It forces the client to connect ot the server through SSL port rather than 80 2) It sends data from client to server encrypted! 3) It provides a certificate from the third party (SSL provider) that we are the rightful owners of this website!
I've been apointed the task of looking through some code for security risks. Up until now it's been PHP, but now a person want's me to look through ASP and ASP.Net files.
The problem is that I don't really know what to look for. Can someone tell me. As many things as possible. in as much detail as possible. even things that normally aren't very risky.
I'd like to start using global.asa to store things like connection strings to databases and the like. As I understand it, you have to save the file in the root of your app.
My concern is that storing the location of databases within the ASA file might be a security issue. Is there any way for a user to get at the information contained in that file and, by extension, get at the databases themselves?
I'm not really asking about "someone stole my credit card info through cookies".
Here's the deal:
I have 2 sites (different domain names) running from one server. One is SSL the other is not. The SSL site has a login and password, which return the user's unique id, which is stuck into a session cookie.
This cookie is then checked at every page because every page is built based on the user's id. If it is not present, the user is redirected to the login page. If the id is wrong, there will be no information shown on the page.
My question is this, can the other (non-SSL) web site see this cookie? The site has no asp or anything else, but if someone "broke into" the non-secure site, could they read the cookie from the other site?
If I store login information in a cookie is it possible for the PC owner to modify the cookie without it making it valid?
For example if in the cookie I store the current user, say "Bob" - if Bob edits his cookie by hand to say "Alan" will the server accept the cookie as valid? Or will it realise that it has been tampered with and discard it?
Anyone recommend a good reference on this sort of thing?
my system is at testing phase. how do i test my system to check its security especially at the login page? i am running it at localhost. i have tried sql injection but nothing happened. i just saw the invalid login username or password error only.
you know when you have a browser based application (written in ASP or whatever), which uses a database, how can you ensure that the username and password of the database is secured? My ASP application has got a file containing all the information you need to connect to the SQL database, if anyone happens to get hold of that file on the Web server then he'll be able to do anything he wants.is there a safer way to handle this?
I just finished my database. There is one problem however, I had to give write permissions to my file with the extension mdb its an access file. The thing is that now all anyone has to do is figure out the page name and their browser will begin to download my database.
That is a major security hazard, what the heck do I do. Am I supposed to just hope no one ever figures out what that specific page name is ?
I was wondering if anyone could help me with a querystring problem. My problem is that users are assigned certain parts of a document, therefore users can only view parts of the document that they have been assigned.
The page with the document is called document.asp and when a user is assigned part of the document they are given a link to the document.asp with the section id in the querystring.
For example a user may be only allocated section 1 of the document. The link they receive has section=1 in the querystring. When clicked the link takes them to the document.asp. The header of the document.asp contains the following: Code:
