asp classic - ASP Login page for ASP.NET Application -


In my workplace, we have several classic ASP and ASP.NET applications.

Although all these applications are integrated through a single sign mode, doing separate tasks, which are controlled by a main application.

The main application is in classic ASP and verifies user ID and password initially and then stores the user ID in the session variable, which is then validated by all other ASP and ASP.Net pages. Used as a user. (For Dot Net pages we use session bridging)

Is this a classic ASP certified? (I do not know the classic ASP)

Since that time I was introduced for this setup, I need to worry that this setup is innocent. Is there a better way to do this?

Is it possible to get certified for both classic ASP and DOT net in the same login page?

What have I always done about my classic ASP applications that you have described when the user logs in Then their credentials are authenticated and then user ID and other relevant information is stored in the session cookie.

The potential flaw in this approach is that in theory, users can change their session cookies locally, so when they request for your application, they are another user who is a security risk. The way I usually find it around, when I store the user's information in the session cookie, I generate an authentication code based on this information and some hidden information (in particular I am SRA 256 I make a string of information and makes a hash).

Then you can check the authentication code regularly to see if it matches the expected code for that user, the cookie must be changed in any way, the authentication code is expected. The code will not match the code and the user will be booting

The main issue in doing something like this is that both the ASP and ASP.NET are getting the implementation of the hashing algorithm which is given Returns the same head value for the output string - or to make sure that you convert it appropriately. / P>

Personally I have used free SHA256 implementation of freeze for Classic ASP, which gives the result as 64 case hex less case string while I system for ASP.Net. Security Cryptography is used. As a result of AME but the upper case (there are some things in it - see the examples given below) so you just have a simple case conversion call.

The function SHA256 (in the form of a biline input string) byteInput () as a byte dim bytHash () as the byte dim objBuilder New StringBuilder Dim objCrypto as new SHA256 managed interior IITINT = encoding ASCII.GetBytes (Input) objCrypto = New SHA256 Managed () bytHash = objCrypto.ComputeHash (bytInput) for intI = 0 UBound (bytHash) objBuilder.Append (hex (byHHash (intI)) Return to next Objbuilder.ToString () End Function

Comments

Popular posts from this blog

c# - ListView onScroll event -

PHP - get image from byte array -

Linux Terminal Problem with Non-Canonical Terminal I/O app -