Is that limitation of WebServerConnector or something fishy?

We have set new server as IIS --> WSC --> Our Security Filter --> WC --> FM

When we address the Security Filter on port 591 directly, everything works as always.

When we are going through IIS and WSC, everything works OK, but not the passwords!

There is no documentation whatsoever about WSC.

Gee Anatoli, I really am sorry to hear about this problem. I surely don't know the answer for using FMPro's password protocol.

It is because of FMPro's password protocol that I made my own protocol utilizing a protected ScriptMaker script.

Is WSC striping the password from the URL?

Garry

I do not understand. There is not URL, just the dialog box to be filled up!

Ah, so it is IIS security that you are using; not FM Web Security?

Garry

--> Our Security Filter -->

No IIS. The FM Web Security Database.

We run this all solutions for 3 years from WC protected by Web Security Databases.

Actually not really protected at all, but that is another issue with failure of FMI protection.

On new server we set the Web Connector and since that the Web Security Database dialogs are not working properly.

It makes absolutely no difference if our own Security Filter is present or not.

Obviously there is also my FM/CDML programmed security as what user can do so this is protecting each user records. User can only amend his/hers record, but not somebody else.

For general posting we implemented the Web Security Databases limited access to add new articles. That is not working through Web Server Connector.

It is not really that bad. We have full anti-hacker Security Filter in place. And I can redesign the workflow for my own evaluation-programmed security.

It is just pity, that FM again failed to test properly the Web Server Connector for this aspect.

It looks like the whole exercise with Web Security Databases is for nothing at all. Hackers can get all the data (not from our server) and it doesn't cooperate with Web Connector. And there is no serious documentation as with almost everything going from Apple culture. In comparison with Linux or even MS it sucks.

As we are producing more and more sophisticated solutions we are having more and more problems with FM stuff.

RE: As we are producing more and more sophisticated solutions we are having more and more problems with FM stuff.

Well that is the conclusion that we are coming to ..... we have avoided many of the problems by moving to Lasso but the limitations of FMPro are beginning to stop us from developing our solutions to the level we would like.

- WSC is a great idea, but I have never got it to work, what I consider, "properly" with Lasso -

We will be moving to Lasso V later in the year ....... we will see how things go with mySQL.

Having said all that we will still use FMPro for some of our smaller accounts. It has been very good for our company - we wouldn't be where we are now if it wasn't for FMPro making it possible for us to get into the market place with a decent, reliable and quick to develop solution at the right price.

It is a shame that FMPro isn't able to (or has chosen not to) grow with us in the same way Lasso has.

Well said. Let us know all news about real performance with Lasso and another databases, please.

About MySQL I've heard just contradictory reports, like "It is slower, than FM" and "it is faster, than FM".

Hi Anatoli

I'll let u know how it goes..... it would be good to hear from anybody who is using mySQL and Lasso already (I know this is an FM forum but it is related to Lasso ). Any descriptions of other peoples' setups would be very helpful

Did you try making sure you have a domain username and password setup identical to the FMP username and password. I seem to recall reading somewhere where IIS will require that to pass the name and password through...worth a shot Thanks...Joe

Sure we are going to try it!

Thanks a lot!