I think he knows how but didnt want to do the whole login process and was asking for a diff way.

well if you have access to the IIS MMC then you can emulate .htaccess from there - but if you don't (as is the case in most hosted instances) you'll have to roll your own in ASP, ASP.NET or CFM

You can use web.config to do a lot of what he is asking to do. You can secure indiviual directories etc and store the usernames & passwords right there if the user base is small enough.

i was just saying he want to stay away from doing it through a db

the web.config way is what I would look into though - that should be quick & easy enough

iknow scott, really wasnt ?'ing that, just were ppl keep going back to the db part, which is what he didnt want but I think he may have already done

I'm agreeing with you........

It amazes me that you almost have to write code for such a common need. The code may be simple for most of you but it's another thing for amateurs like me to learn. I wish FrontPage had a simple interface to a standard web permissions protocol, but since that's a dream for now, I wish HMS could offer an interface to their permissions feature.

Well, web.config isn't very complicated, nor is it very hard. Check this out... http://www.dotnetcoders.com/web/Articles/ShowArticle.aspx?article=186

Goto the bottom of the page... copy and paste one or both examples into a file called "web.config" (without the quotes) and marvel at the beauty of ASP.NET btw, you can't do that with ColdFusion MUAH HA HA!!!

It's done this way to give you nearly total control over the security of your website and maximum flexibility. In .NET it's MUCH easier than it was before. It's still easier to do it in Apache with the .htaccess but that's another story altogether and the .htaccess can be just as cryptic.

Here are a couple links to some good articles on configuring directory security using forms authentication in a .NET environment...

http://www.dotnetcoders.com/web/Articles/ShowArticle.aspx?article=186
http://www.wwwcoder.com/main/parentid/258/site/4340/68/default.aspx

The first one seems to nearly emulate the .htaccess approach to directory security - probably about as close as you can get with .NET

umm ok josh, it's actually easier in coldfusion

Application.cfm or now Application.cfc now

What's a .cfc?

j/k

your fav thing!

How would you implement that in your Application.cfm?

well it is fairly easy but first thing is you need to get far far far far far far away from frontpage!!!
I wish frontpage had a lot of things but would take days to describe them all.

You have to write code for it because there are so many ways that you can use it and it's very important, security on a site is no laughing matter, hence why frontpage probably doesn't offer it, frontpage is already so insecure that it's shamefull.

If you are making a site or sites and you are on these forums then you obviously are interested enough in doing this to do it right.
You can search archives here for a ton of frontpage related stuff so you can understand how frontpage will limit you and your website visitors.

Also with the new version of coldfusion and dreamweaver it has a built-in amazing login wizard that is basically what you are asking for.

Bottom line, if I was you I would move to dreamweaver and start to learn a server side language like cfm, .net or php.
But get away from frontpage! And that's not me hatin m$ or fp that's just good advise

lots of possible way
see the Application.cfm file is run at each request before any code, so you put things in that file that you would like run and you can have lots of them (just not more than 1 per folder).

So say you have a folder, in this case the folder is the one he wants to protect, just put your Application.cfm file in there .

lets say in this case he doesnt want to do the whole login thing and decides that he wants to limit access to the folder by the users IP address.





so what that does is everythimg a page from that file is requested it checks the users ip and if its good it lets them go on if not it gives an error message