no password in Web Security?

[timmy]

I have a server hosting multiple databases. All of these databases are passworded using the Web Security Database. The problem is this:

I want to add one more database that will be viewed by the general public. This means that I dont want there to be any password to this database, and I want users to have browse only permission.

I know that I can set this using the FileMaker access privileges, but since I have those other databases, it seems that i'm stuck using Web Security Database.

What to do?

thanks,

Tim.

[dmartens]

In the Web Security DB add a record for your database with the user All Users, no password, and the privledges set to browse only.

[timmy]

perfect. thanks a million.

[Keith M. Davie]

You need to read this thread:

http://www.fmforums.com/threads/showthreaded.php?Cat=&Board=UBB21&Number=19032&Search=true&Forum=UBB21&Words=chazboi&Match=Username&Searchpage=0&Limit=25&Old=1year&Main=19032

All of it. Do it when you have an hour or more. It is of significant importance.

[ibiubu]

The above mentioned link is FULL of information. In fact it reinforces my opinion about FileMaker...

I love the program. But you keep hearing how FileMaker is trying to get the software widely accepted. I can't see how this will be the case when they have a program (that has been on the market for years) that still continues to show MAJOR security gaps in features that they tout as being the backbone of the software.

Yes, there are fixes for these security gaps. But should users be forced to pony up an additional $500 for something like Lasso, plus the time and cost to implement these solutions. And all just to fix security gaps that should not be there in the first place.

If FileMaker REALLY wants to advance the programs web capabilities to the general user, they REALLY need to fix such things as security (we won't even get into the whole "HTML pages in the FileMaker Web folder" fiasco), not to mention an overdue engine overhaul to solve such problems as script collisions on the web.

Again, I'm not bad mouthing the program, I love it for what it does, would just like to see some of the glaring mistakes fixed. One can only wish, right?

LR

[Garry Claridge]

In that thread some audacious claims were made about the lack of security. Be aware that the 'Web Security' database can be used for most needs. The only glaring omission is record level security; however, it has 'Field' restriction capabilities.

An example of a method for 'Record Level' restrictions is available for download from the FM site.

The other issue, a problem for some but not for others, is the ability to view file and field names.

That's it in a nutshell.

All the best.

Garry