Re: external server authentication and licensing
- From: d-42 <db.porsche@xxxxxxxxx>
- Date: Fri, 15 May 2009 19:13:23 -0700 (PDT)
On May 15, 4:41 pm, Chris Brown <cbr...@xxxxxxxxxxxxxxxxxxxxxxxx>
wrote:
ESA from the FM documentation is the recommended method as I interpreted
it. It is a booking system so security is an issue.
External Authentication is the "recommended" solution because it
integrates with an organizations existing centrally managed systems
(e.g. Apple Open Directory or Windows ActiveDirectory).
It's not inherently more secure. Its not inherently better.
Its just really convenient if you already have all these accounts and
groups set up -- and then you can have filemaker's security integrate
with it and manage it all centrally. This beats having to recreate and
manage them again separately in filemaker.
But if an organization doesn't manage these external accounts in
active directory, and the ONLY purpose for creating these accounts is
to manage access to filemaker, there is really no point to it at all.
It anything its just a whole lot of extra needless clutter in what
was, until now, a simple SBS setup; with the added bonus, that if you
have any trouble with active directory, your website goes down too.
As stated, my understanding is that ESA is the recommended method.
Recommended for organizations that can derive some sort of benefit
from having all the accounts in active directory... usually because
all those accounts already are in active directory.
Implementing active directory for 1000 external accounts, upgrading
SBS to Standard server, and purchasing the External Connector license,
all for the sole purpose of managing access to filemaker is, no
offense, absurd.
If SMB itself is the issue, and vanilla windows server
(2003/2008) as the domain controller allows unlimited users, then this
would be the comfortable option.
Nobody sets up a 1000+ Active Directory accounts for external
customers simply to manage access to a database driven website.
-regards,
Dave
.
- Follow-Ups:
- Re: external server authentication and licensing
- From: Chris Brown
- Re: external server authentication and licensing
- References:
- external server authentication and licensing
- From: Chris Brown
- Re: external server authentication and licensing
- From: d-42
- Re: external server authentication and licensing
- From: Chris Brown
- external server authentication and licensing
- Prev by Date: If a field contains a specific text string, put a colon after the contents of that field; if not, put a comma
- Next by Date: Re: If a field contains a specific text string, put a colon after the contents of that field; if not, put a comma
- Previous by thread: Re: external server authentication and licensing
- Next by thread: Re: external server authentication and licensing
- Index(es):
Relevant Pages
|