My user table contains a bit more than user ID and password. I'm thinking of using the ElevateDB built in User/Password and linking with my users table for the additional information.

What are you others doing / planning on doing?


Roy Lambert

CREATE TABLE "Users"
                    (
                    "_ID" VARCHAR(5) COLLATE "ANSI",
                    "_BoxBase" INTEGER GENERATED BY DEFAULT AS IDENTITY (START WITH 6, INCREMENT BY 1),
                    "_Name" VARCHAR(60) COLLATE "ANSI",
                    "_Title" VARCHAR(40) COLLATE "ANSI",
                    "_DirectDial" VARCHAR(25) COLLATE "ANSI",
                    "_fkProjects" INTEGER,
                    "_ConectInfo" VARCHAR(40) COLLATE "ANSI",
                    "_Check" VARCHAR(30) COLLATE "ANSI",
                    "_CheckDate" DATE,
                    "_SUOP" VARCHAR(11) COLLATE "ANSI",
                    "_Privileged" BOOLEAN,
                    "_Permitted" BOOLEAN DEFAULT FALSE,
                    "_Group" VARCHAR(15) COLLATE "ANSI",
                    "_Sig" INTEGER,
                    "_MRU" CLOB COLLATE "ANSI",
                    "_Notes" CLOB COLLATE "ANSI",
                    "_FilterStore" CLOB COLLATE "ANSI",
                    "_AutoLoads" CLOB COLLATE "ANSI",
                    "_Tasks" CLOB COLLATE "ANSI",
                    "_UserOptions" CLOB COLLATE "ANSI",
                    "_PageIndices" CLOB COLLATE "ANSI",
                    "_DisplaySettings" CLOB COLLATE "ANSI",
                    CONSTRAINT "PrimaryKey" PRIMARY KEY ("_ID")
                    )

Roy,

<< My user table contains a bit more than user ID and password. I'm thinking
of using the ElevateDB built in User/Password and linking with my users
table for the additional information. >>

As a quick note, one of the items I'm looking into is virtualizing the
configuration so that the users/roles can be "outsourced" to the application
or server and be routed through the OS or some other external authentication
mechanism.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim

>As a quick note, one of the items I'm looking into is virtualizing the
>configuration so that the users/roles can be "outsourced" to the application
>or server and be routed through the OS or some other external authentication
>mechanism.

You're sounding more like a geek all the time

I hope its nothing like Vista virtualisation - you know the "I keep changing my file and it keeps getting reset" or the "where the hell has my data gone now" variety.

What other bits might this apply to? and of course timescales (at least for a decision so I can make one as well)?

Roy Lambert

Roy,

<< You're sounding more like a geek all the time >>

Umm, I've been writing database engines for the past 11 years - at what
point did I stop being a geek ????

<< I hope its nothing like Vista virtualisation - you know the "I keep
changing my file and it keeps getting reset" or the "where the hell has my
data gone now" variety. >>

No, no, no....more like "here, you handle the creation, storage, etc. of the
authorizations, database definitions, etc. and just give me the information
that I want about them when I ask for it.

<< What other bits might this apply to? and of course timescales (at least
for a decision so I can make one as well)? >>

No way, no timescales at this stage.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim


>Umm, I've been writing database engines for the past 11 years - at what
>point did I stop being a geek ????

I never said you weren't one just that your posts sound more like one than they used to

>No, no, no....more like "here, you handle the creation, storage, etc. of the
>authorizations, database definitions, etc. and just give me the information
>that I want about them when I ask for it.

That sounds very interesting

>No way, no timescales at this stage.

Unfair - all I wanted was a timescale as to when you would make a decision to go that way, not when can I have it

Roy Lambert

Roy,

<< Unfair - all I wanted was a timescale as to when you would make a
decision to go that way, not when can I have it >>

Once I mention it, I usually have already decided to go in that direction in
some form or another.   The end result may be a little different, but the
general idea will be the same.  Basically the idea is to allow for using
3rd-party security frameworks and/or Windows authorization in an integrated
fashion with EDB.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim


OK then I'll stick to rolling my own security in the hope that someday I'll be able to integrate with yours.

Roy Lambert

Roy:

Did you ever implement this? (see below).  If so, how is it working for you?  I'm thinking
of doing the same thing.

Thanks,

Dale



Roy Lambert <roy.lambert@skynet.co.uk> wrote:

My user table contains a bit more than user ID and password. I'm thinking of using the
ElevateDB built in User/Password and linking with my users table for the additional
information.

What are you others doing / planning on doing?


Roy Lambert

CREATE TABLE "Users"
                    (
                    "_ID" VARCHAR(5) COLLATE "ANSI",
                    "_BoxBase" INTEGER GENERATED BY DEFAULT AS IDENTITY (START WITH 6,
INCREMENT BY 1),
                    "_Name" VARCHAR(60) COLLATE "ANSI",
                    "_Title" VARCHAR(40) COLLATE "ANSI",
                    "_DirectDial" VARCHAR(25) COLLATE "ANSI",
                    "_fkProjects" INTEGER,
                    "_ConectInfo" VARCHAR(40) COLLATE "ANSI",
                    "_Check" VARCHAR(30) COLLATE "ANSI",
                    "_CheckDate" DATE,
                    "_SUOP" VARCHAR(11) COLLATE "ANSI",
                    "_Privileged" BOOLEAN,
                    "_Permitted" BOOLEAN DEFAULT FALSE,
                    "_Group" VARCHAR(15) COLLATE "ANSI",
                    "_Sig" INTEGER,
                    "_MRU" CLOB COLLATE "ANSI",
                    "_Notes" CLOB COLLATE "ANSI",
                    "_FilterStore" CLOB COLLATE "ANSI",
                    "_AutoLoads" CLOB COLLATE "ANSI",
                    "_Tasks" CLOB COLLATE "ANSI",
                    "_UserOptions" CLOB COLLATE "ANSI",
                    "_PageIndices" CLOB COLLATE "ANSI",
                    "_DisplaySettings" CLOB COLLATE "ANSI",
                    CONSTRAINT "PrimaryKey" PRIMARY KEY ("_ID")
                    )

Dale


Yup, my users file now contains no password Mind you all users in ElevateDB are created with full and total access.

Roy Lambert