Filemaker Passwords 
Author Message
 Filemaker Passwords

Hi,

I know that by defining passwords and then associating them with groups, I
can use stats(currentgroups) to get the groupname and perform any required
validation.

Is there anyway that I can check the current password ? I cannot seem to
find a function to do this anywhere.

I am using different passwords to control access to an entire file by
breaking it down into sales areas, each sales person having access to only
their records by limiting access in the password (defin access priv.)
section.

So, any given password only has access to records in their area as
controlled by a region code, this is fundamental belt+braces solution that
will stop anyone ever seeing records that they should not (as far as I can
tell).

On entering the system, I need to perform a find to make sure that they can
start by seeing their records so I would like to check the password and then
perform find/restore accordingly.

Right now I can see that I could associate a unique password with a unique
group - however I am having trouble making this work.

I feel confident that there must be a better way but the existing
application is vast and I have dismissed (so far!) any thoughts of
re-writing it in order to perform some form of exclusion/seggrigation as
almost every script might have to change. Hence the use of limiting access.

Any ideas would be great,

Kind regards

Richard Scales



Tue, 17 May 2005 14:29:37 GMT
 Filemaker Passwords

Go to waves-in-motion website.
There is a new solution for you, which does exactly what you need.

http://wmotion.com/securitymanager.html

/Steve

Quote:

> Hi,

> I know that by defining passwords and then associating them with groups, I
> can use stats(currentgroups) to get the groupname and perform any required
> validation.

> Is there anyway that I can check the current password ? I cannot seem to
> find a function to do this anywhere.

> I am using different passwords to control access to an entire file by
> breaking it down into sales areas, each sales person having access to only
> their records by limiting access in the password (defin access priv.)
> section.

> So, any given password only has access to records in their area as
> controlled by a region code, this is fundamental belt+braces solution that
> will stop anyone ever seeing records that they should not (as far as I can
> tell).

> On entering the system, I need to perform a find to make sure that they can
> start by seeing their records so I would like to check the password and then
> perform find/restore accordingly.

> Right now I can see that I could associate a unique password with a unique
> group - however I am having trouble making this work.

> I feel confident that there must be a better way but the existing
> application is vast and I have dismissed (so far!) any thoughts of
> re-writing it in order to perform some form of exclusion/seggrigation as
> almost every script might have to change. Hence the use of limiting access.

> Any ideas would be great,

> Kind regards

> Richard Scales



Tue, 17 May 2005 23:38:01 GMT
 Filemaker Passwords
I am having trouble understanding what you are after. Are you trying to make
some records off-limits to certain users?

FMP 5.5 introduced record and field level security, although I haven't heard
much good about their use (I've not tried). It's much easier to control
access by layout, but turning that into a method for managing access at the
record level would be a daunting task, even if you were starting from
scratch. Re-modelling is always harder than new construction.

To do so, a toggle field (number is easiest) could be added to the relevant
files, and all movement locked down and controlled by scripts. All important
activities would include a test for the Boolean state of the toggle field
(on or off-- 1 or 0), and a test for Status(CurrentGroups):

If [Toggle]
  If[PatternCount(Status(CurrentGroups), "Lowdown" )]
    Show Message ("Sorry, too lowdown.")
  End If
    Else
    If[PatternCount(Status(CurrentGroups), "BigCheese" )]
      Do Stuff
    End If
End If

Obviously, don't place Toggle on any layout, and toggling it would be
entirely scripted, dependent itself on a test for group level.

No, there is no native way to check the current password.

--
John Weinshel
Datagrace
Vashon Island, WA
(206) 463-1634
Associate Member, Filemaker Solutions Alliance


Quote:
> Hi,

> I know that by defining passwords and then associating them with groups, I
> can use stats(currentgroups) to get the groupname and perform any required
> validation.

> Is there anyway that I can check the current password ? I cannot seem to
> find a function to do this anywhere.

> I am using different passwords to control access to an entire file by
> breaking it down into sales areas, each sales person having access to only
> their records by limiting access in the password (defin access priv.)
> section.

> So, any given password only has access to records in their area as
> controlled by a region code, this is fundamental belt+braces solution that
> will stop anyone ever seeing records that they should not (as far as I can
> tell).

> On entering the system, I need to perform a find to make sure that they
can
> start by seeing their records so I would like to check the password and
then
> perform find/restore accordingly.

> Right now I can see that I could associate a unique password with a unique
> group - however I am having trouble making this work.

> I feel confident that there must be a better way but the existing
> application is vast and I have dismissed (so far!) any thoughts of
> re-writing it in order to perform some form of exclusion/seggrigation as
> almost every script might have to change. Hence the use of limiting
access.

> Any ideas would be great,

> Kind regards

> Richard Scales



Wed, 18 May 2005 01:39:57 GMT
 Filemaker Passwords
Indeed - I want to make certain records (controlled by a code in a
particular field) to be 100% off limits to all but authorised users. This is
essentially to control sales areas and leads that are automatically loaded
into the system should only be viewable by the correct sales people
depending on their designated area.

As there are many many finds and find restores scripted in the application,
the task of adding this control is daunting indeed. Initial testing done
using the Filemaker in-built controls seem to work very well.

I will need to allocate passwords to each individual.

Those passwords will then be allocated to different groups - one group for
each sales area - thus I can indeed test for group membership. I will need
this to make sure that when starting up or 'finding all' I can at least find
records for the required area and not leave users staring at a screen full
of 'access denied' messages.

The individual passwords have the access control formula applied to them in
the define aceess priv. section.

I believe that this is going to be the quickest and easiest method of
implementing this seggregation in the existing application.

What do you think ?

Richard Scales


Quote:
> I am having trouble understanding what you are after. Are you trying to
make
> some records off-limits to certain users?

> FMP 5.5 introduced record and field level security, although I haven't
heard
> much good about their use (I've not tried). It's much easier to control
> access by layout, but turning that into a method for managing access at
the
> record level would be a daunting task, even if you were starting from
> scratch. Re-modelling is always harder than new construction.

> To do so, a toggle field (number is easiest) could be added to the
relevant
> files, and all movement locked down and controlled by scripts. All
important
> activities would include a test for the Boolean state of the toggle field
> (on or off-- 1 or 0), and a test for Status(CurrentGroups):

> If [Toggle]
>   If[PatternCount(Status(CurrentGroups), "Lowdown" )]
>     Show Message ("Sorry, too lowdown.")
>   End If
>     Else
>     If[PatternCount(Status(CurrentGroups), "BigCheese" )]
>       Do Stuff
>     End If
> End If

> Obviously, don't place Toggle on any layout, and toggling it would be
> entirely scripted, dependent itself on a test for group level.

> No, there is no native way to check the current password.

> --
> John Weinshel
> Datagrace
> Vashon Island, WA
> (206) 463-1634
> Associate Member, Filemaker Solutions Alliance



> > Hi,

> > I know that by defining passwords and then associating them with groups,
I
> > can use stats(currentgroups) to get the groupname and perform any
required
> > validation.

> > Is there anyway that I can check the current password ? I cannot seem to
> > find a function to do this anywhere.

> > I am using different passwords to control access to an entire file by
> > breaking it down into sales areas, each sales person having access to
only
> > their records by limiting access in the password (defin access priv.)
> > section.

> > So, any given password only has access to records in their area as
> > controlled by a region code, this is fundamental belt+braces solution
that
> > will stop anyone ever seeing records that they should not (as far as I
can
> > tell).

> > On entering the system, I need to perform a find to make sure that they
> can
> > start by seeing their records so I would like to check the password and
> then
> > perform find/restore accordingly.

> > Right now I can see that I could associate a unique password with a
unique
> > group - however I am having trouble making this work.

> > I feel confident that there must be a better way but the existing
> > application is vast and I have dismissed (so far!) any thoughts of
> > re-writing it in order to perform some form of exclusion/seggrigation as
> > almost every script might have to change. Hence the use of limiting
> access.

> > Any ideas would be great,

> > Kind regards

> > Richard Scales



Thu, 19 May 2005 03:20:24 GMT
 
 [ 4 post ] 

 Relevant Pages 

1. cracking FileMaker passwords

2. FileMaker password auto-enter

3. Filemaker passwords

4. RE Filemaker PASSWORDS

5. FileMaker Password

6. FileMaker ODBC Password

7. Filemaker and passwords

8. Password protection for Filemaker Server admin

9. Password Encryption for Filemaker Server 5.5

10. Mac FileMaker Pro default Password OverRide

11. FileMaker and passwords

12. how secure are groups / passwords in filemaker?


 
Powered by phpBB® Forum Software