Yesterday we received the complete Filemaker 5.5 package (Server 5.5, Unlimited 5.5, Developer 5.5, Pro 5.5, WSC + Tools).

After installing the Server 5.5 package, I quickly found out that the NT Authentication doesn't do what you expect it to do. It only ask the user to enter it's username/password/domain if the user isn't logged on to a trusted domain. After that you can't do a thing with the username (no status functionality...), conclusion: NT Authority doesn't work!

As for Filemaker Developer 5.5: THIS PRODUCT RULES!

We're now able to create a full Database Design Report in XML or as an Filemaker Database and finally the Scripts can be debugged an executed step-by-step.

I'm really dissapointed of the NT Authentication part. Let's hope that Filemaker 6.0 contains full NT Authentication so you can serve databases with fm unlimited from a fm server via the web and require your web-users to enter their NT username/password/domain combination in order to get access...

(I'll post that last part in the Future Requists, maybe they listen.. )

Well, on with the Web Security database again then.

Greetz,

Jorick Schram

All-Round & Multi-Platform Developer

VODW Marketing

The Netherlands

"...full NT Authentication so you can serve databases with fm unlimited from a fm server via the web and require your web-users to enter their NT username/password/domain combination in order to get access..."

OK, I'll show my ignorance. I have no idea of what "NT Authentication" consists or how it works with the www.

I fail to understand your complaint since I do know that FileMaker will allow you to set up your own username/password/domain (or any other combination you could want)if you want entry restrictions. All you need to do is create it. You can even set this up while employing an "all users" Web Security permission.

SIMPLIFY ...

Keith

quote:

---

Originally posted by Keith M. Davie:

"...full NT Authentication so you can serve databases with fm unlimited from a fm server via the web and require your web-users to enter their NT username/password/domain combination in order to get access..."

OK, I'll show my ignorance. I have no idea of what "NT Authentication" consists or how it works with the www.

I fail to understand your complaint since I do know that FileMaker will allow you to set up your own username/password/domain (or any other combination you could want)if you want entry restrictions. All you need to do is create it. You can even set this up while employing an "all users" Web Security permission.

SIMPLIFY ...

Keith

---

The point is that I'm not too lazy to set up the Web Security database, but that our users don't want to remember more than one username/password combination.

You see, our users are people that don't use the computer as a primary working-tool, so it shouldn't be too complex for them. They just make some letters in Word, some presentations with Powerpoint, read and send mail with Outlook, surf the internet for a bit and register what ours they spent working on a project. The last part will be going via the Intranet soon, and it shouldn't be necesary for them to have an other username/password combination for the Intranet, otherwise they might not use it and that costs the finance department much time..

Maybe there's someone out there who created a plug in for this problem?

quote:

---

Originally posted by Anatoli:

If you will make some autolog procedure, let people log once and save their bookmark inclusive of their Name and password, then nobody is forced to remember something.

---

That would work but then it isn't as dynamic as it was ment to be. You see, the beauty of a web-based application lies in the fact that you can access it from everywhere (at the office, at the customers or at home via VPN)

If you will make some autolog procedure, let people log once and save their bookmark inclusive of their Name and password, then nobody is forced to remember something.

"After installing the Server 5.5 package, I quickly found out that the NT Authentication doesn't do what you expect it to do. It only ask the user to enter it's username/password/domain if the user isn't logged on to a trusted domain. After that you can't do a thing with the username (no status functionality...), conclusion: NT Authority doesn't work! "

The only thing I know is, that Microsoft WebServer IIE (InternetInformationServer) uses a default user for connections from the Internet!

Do you use IIE or FMP 5.5 as WebServer on your NT?

In case you have IIE installed, try to give the NT default User for Internet "inetuser" read and execute privilege on your Web-Root-Folder.

In case you use FMP 5.5 as WebServer, try to give the user "alluser" read and execute privilege on your web-root-folder.

The LAN users can use differnet cdml/html pages to the Internet users. The LAN users pages can have [FMP-InlineAction] tags which "auto-enter" a username and password for the WebSecurity database.

I'm assuming that LAN users are 'trusted' users.

All the best.

Garry

quote:

---

Originally posted by Jorick Schram:

That would work but then it isn't as dynamic as it was ment to be. You see, the beauty of a web-based application lies in the fact that you can access it from everywhere (at the office, at the customers or at home via VPN)

---

Why not? I can and everyone can as well. It is just the hustle with logins.

For me it is the same to type my access into URL or dialog pop box

"The point is that .. our users don't want to remember more than one username/password combination."

Well if you set up the username/password in cdml, your users can initially register (login) with whatever "one username/password combination" they are already comfortable with, and on subsequent visits they can access through their previously registered (logged-in) "one username/password" with which they are comfortable.