I have been wanting to write a blog on this topic like forever. Finally I have got down to write down the brief explanation.
IIS 6 authentication is of different types and is capable of delivering the needs of various scenarios.This blog is going to provide you with the best way to learn concepts of IIS 6 authentication.
Well from then on, it depends on how you want to take this article too. Put down your comments and I will try and stitch the various questions to another blog on this topic. I am pretty sure IIS authentication raises a lot of questions in the mind of the reader. So here it goes.
The 2 concepts which often confuses a lot of people are - authentication and authorization. Lets start by 1st differentiating them
Authentication is the process of obtaining credentials from the users and using those to verify the user's identity. These credentials can be received in many ways and can be of many types. Whereas, Authorization is the process of allowing an authenticated user access to resources.For example, in IIS 6 if you use Basic Authentication then the username and password are transmitted over the network in plain text format.
Lets understand this with the help of an example. I am going to consider that we are working with anonymous access. The usual misconception that people have is that with Anonymous access everyone can view anything on the server. Well that is not true!
Authentication always precedes Authorization; even if your application lets anonymous users connect and use the application, it still authenticates them as being anonymous.
Assume, if the authenticated user does not have privileges on the content that is to be viewed, the user is not authorized to view the content.The important point to understand here is that the user is never the less still authenticated.
The different types of Authentication available in IIS 6 are:
(For the sake of me not typing duplicate material, I have given the appropriate links which explains the phenomenon the best ;) )
- Anonymous Authentication. (Microsoft Explains)
- Digest Authentication for Windows Domain Users. (Microsoft Explains)
- Integrated Windows Authentication. (Microsoft Explains)
- Basic Authentication. (Microsoft Explains)
- .Net Passport authentication. (Microsoft Explains)
Incorrect settings may lead to certain errors depending upon the configuration that may have gone wrong. But mostly you may come across a 401.x or 403.x errors. For description on these errors view my previous blog on understanding the status and substatus code
Will be coming about with a few more articles on IIS authentication in the near future. Just need to decide how to go about it :D
Posts
3 comments:
I think your explanation of how to find the logs files is misleading.
It doesn't explain how to get the log file location. And the default directory is logfiles not logsfiles. ;)
I would have said something like (cut and past from a beginners log files guide I am writing at work atm) :
For IIS 6
They are located:
Select Website --> Properties --> Web Site tab --> Under Enable Logging select Properties
This gives you the log file directory.
The default of this is C:\windows\system32\LogFiles\ but this is not always the case.
And the log file name (additional directory and the .log file in exYYMMDD format is appended to this)
e.g.
d:\inetlogfiles\w3svc6725176\ex080613.log
Remember that there are multiple servers in the farm so you will have to check them in each server.
My approach towards the log files was to find it through the explorer, and yes, I was targeting the default settings with a simple setup ...
I have correct the spelling for the log files directory... Thanks for showing that ... :)
No problem.
Doh! I must have posted under the wrong article this is obviously for ""Troubleshooting: IIS 6 Status and Substatus codes""
Post a Comment