Problem with USER.Identity.name in ASP.net

**Jesse Bas** · 16-07-2009

I know that inn Asp.Net using this "USER.Identity.name" code we can get user logon name.I want to know the exact functioning of this code:
Can anyone here help me since I don't see any output I am getting to know the username.
Is there any setting I must do to get the username on localhost in the IIS?

this.user.identity.name""

**JiJi** · 16-07-2009

I have a question about the Username. Is it true that all users log in with username@domain_name structure? If yes then I wnat to know How this.User.Identity.Name gives the name as we have logged in as? may be its a very simple question but still I want to know this.

**Modifier** · 16-07-2009

Try this for VB.Net:
User.Identity.Name

Code:

<%@ Page Language="vb" %>
<html>
   <head>
      <title>User property example</title>
      <script runat="server">
         Sub Page_Load()
            Message.Text = "Authenticated: " & User.Identity.IsAuthenticated & "<br/>"
            Message.Text &= "User Name: " & User.Identity.Name
         End Sub
      </script>
   </head>
<body>
   <asp:label id="Message" runat="server"/>
</body>
</html>

For ASP.net

Code:

<%@ Page Language="vb" %>
<html>
   <head>
      <title>Displaying the authentication status in ASP.NET</title>
   </head>
<body>

<p>

<%
   Dim boolAuth As Boolean

   boolAuth = Request.IsAuthenticated

   If boolAuth Then
      Response.Write("User " & Page.User.Identity.Name & " is authenticated.")
   Else
      Response.Write("Current user is not authenticated.")
   End If
%>

</p>

</body>
</html>

**Zombi** · 16-07-2009

ASP.NET Request Identity

ASP.Net supports the following authentication modes, None, Windows and Forms. None as it's name implies does not perform any type of authentication and runs under the default identity. Windows supports both basic and integrated authentication. Forms supports the ASP.Net forms authentication.
As part of the ASP.Net request life cycle, we can capture the AuthenticateRequest event when a request is received. This event always fires and is raised by the Application. It can be handled in the Global.asax. This event is also handy for capturing the actual user's identity and replacing the users principal with our own.