Skip to Content

Introduction :-

In these days every one wants to secure their portal resources no matter how big or how small. By securing we mean that careful managing of our resources. These days we can acheieve authentication through various means. The simplest of them is web based authentication. In this blog we can see the various options an user has to handle authentication using a web application server.The below table will lists the options available.

13.5pt;color:black’>Authentication Options In WAS :-

style=’color:black’>Although we have defined the users that are allowed access to a resource, we need to tell the container how we want to authenticate the users. There are four authentication methods to choose from:

style=’color:black’>Authentication Method style=’color:black’>

style=’color:black’>Description style=’color:black’>

mso-bidi- color:black’>BASIC style=’color:black’>

style=’color:black’>Use HTTP basic authentication. If we used this setting window will show trying to mso-bidi-font-size: 12.0pt;color:black’>secure style=’color:black’>.

mso-bidi- color:black’>FORM style=’color:black’>

style=’color:black’>It is sometimes nice to be able to build your authentication into your Web pages. With FORM-based authentication we can do this. Already we have seen Form based authentication in WAS in my previous   blog.

mso-bidi- color:black’>CLIENT-CERTIFICATE style=’color:black’>

style=’color:black’>Uses client digital certificates to authenticate.

mso-bidi- color:black’>DIGEST style=’color:black’>

style=’color:black’>Use HTTP digest authentication Mechanism.

 

 

Conclusion :-

This short blog is just an snapshot of Authentication options available for us in WAS. In future we will see much more interesting details in this topic.

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply