Hi All,

Just wondered what's the correct event to use to trap an incorrect login
on a EDB Server application? Reason being I want to then call a function
that writes a record to a log file.

I'm using the TEDBEngine's 'ServerEngineServerSessionEvent' with an
EventType of seLogin to write to the log file on a successful login, but
can't for the life of me workout what to use for an unsuccessful login.

Thanks,

Phil.

I don't know if this is what you're looking for, but take a look at this old post from Tim:

Barry

http://www.elevatesoft.com/forums?action=view&category=edb&id=edb_general&msg=7455&start=1&keywords=log%20invalid%20login%20server&searchbody=True&forum=EDB_Announce&forum=EDB_General&forum=EDB_SQL&forum=EDB_Connect&forum=EDB_Extensions&forum=EDB_Beta&forum=EDB_Binaries&forum=EDB_Suggestions&forum=EDB_ThirdParty&forum=EDB_Discussion#7455

Tiago,

<< I meant the case an user inputs valid login name but bad password.  Or
when login retry count is raised.  Currently I can't make log to save any of
both cases. >>

Go into the server interface (System Tray, Right-Click on EDB Server Icon,
Restore), click on the Stop Server task link, click on the Edit Server
Options link, and under the Configuration tab, make sure that the
Information, Warning, and Error check boxes are checked for the Logging
section.

--
Tim Young
Elevate Software
www.elevatesoft.com

> I don't know if this is what you're looking for, but take a look at this old post from Tim:
>
> Barry
>
> http://www.elevatesoft.com/forums?action=view&category=edb&id=edb_general&msg=7455&start=1&keywords=log%20invalid%20login%20server&searchbody=True&forum=EDB_Announce&forum=EDB_General&forum=EDB_SQL&forum=EDB_Connect&forum=EDB_Extensions&forum=EDB_Beta&forum=EDB_Binaries&forum=EDB_Suggestions&forum=EDB_ThirdParty&forum=EDB_Discussion#7455
>

Thanks Barry, that's not quite what I'm after... I have written my own
server program as oppose to using the ElevateDB Server. Reason I had to
do this is, the server does other tasks like importing data from a PABX
phone system and polling a SOAP web service to grab data etc.

So really I'm looking for a way for the server app to detect a failed
login, one I can work out how to do that I can then write to the
auditlog database table I have.

Phil,

>So really I'm looking for a way for the server app to detect a failed
>login, one I can work out how to do that I can then write to the
>auditlog database table I have.

Sure. I was thinking if you have the source code for the EDB server you could see how they intercept failed logins.

Barry

Phil


Have a look at the TEDBSession OnLogin event. That's what I use in fileserver mode and I assume it will be the same for c/s

Roy Lambert

> Have a look at the TEDBSession OnLogin event. That's what I use in fileserver mode and I assume it will be the same for c/s
>
> Roy Lambert

Hi Roy,

Yep that's what I'm using (ServerEngineServerSessionEvent) to log the
successful logins by testing the TEDBServerSessionEventType and writing
the log accordingly... But how to trap an unsuccessful login from the 6
available types???

TEDBServerSessionEventType { seOpen, seConnect, seLogin, seLogout,
seDisconnect, seClose };

Cheers,

Phil.

> Have a look at the TEDBSession OnLogin event. That's what I use in fileserver mode and I assume it will be the same for c/s
>
> Roy Lambert


Sorry Roy I misread your question... You did help me in working it out.

I tried using the TEDBSession OnLogin, but it wasn't getting fired off...

However I ended up using the TEDBEngine's OnServerSessionLogin and that
worked...

In effect what I've ended up doing is... Running a Query on the
Configuration.Users table for a match of the UserName and UserPassword
vars that event gives me and then logging the FAILED or SUCCESSFUL login
depending on the result.

Thanks for your input Roy

Phil,

<< I'm using the TEDBEngine's 'ServerEngineServerSessionEvent' with an
EventType of seLogin to write to the log file on a successful login, but
can't for the life of me workout what to use for an unsuccessful login. >>

Don't use that event, it's not going to be helpful for you.  Do you have to
have the unsuccessful logins in your own database ?  They already exist
here:

http://www.elevatesoft.com/manual?action=viewtopic&id=edb2sql&topic=LogEvents_Table

when at least the Error logging level is enabled in the EDB Server.

I can also see about surfacing an event that pops out the same logged
attributes that EDB will log to the logged events.

Tim Young
Elevate Software
www.elevatesoft.com

> Phil,
>
> << I'm using the TEDBEngine's 'ServerEngineServerSessionEvent' with an
> EventType of seLogin to write to the log file on a successful login, but
> can't for the life of me workout what to use for an unsuccessful login. >>
>
> Don't use that event, it's not going to be helpful for you.  Do you have
> to have the unsuccessful logins in your own database ?  They already
> exist here:
>
> http://www.elevatesoft.com/manual?action=viewtopic&id=edb2sql&topic=LogEvents_Table
>
>
> when at least the Error logging level is enabled in the EDB Server.
>
> I can also see about surfacing an event that pops out the same logged
> attributes that EDB will log to the logged events.
>
> Tim Young
> Elevate Software
> www.elevatesoft.com
>

Hi Tim,

In the end I did this and works perfectly...

I ended up using the TEDBEngine's OnServerSessionLogin and that worked...

In effect what I've ended up doing is... Running a Query on the
Configuration.Users table for a match of the UserName and UserPassword
vars that event gives me and then logging the FAILED or SUCCESSFUL login
depending on the result.

Phil,

<< I ended up using the TEDBEngine's OnServerSessionLogin and that worked...

In effect what I've ended up doing is... Running a Query on the
Configuration.Users table for a match of the UserName and UserPassword vars
that event gives me and then logging the FAILED or SUCCESSFUL login
depending on the result. >>

Cool.  We've got a customer using that event handler to do Windows Active
Directory authentication and automatic group management on login to an EDB
Server, so it's pretty useful.

BTW, just so you know - that event handler will be experiencing a breaking
change for 2.10 and will contain a lot more parameters for the client such
as the process name (computer name+process ID), thread ID, EDB
version/build, etc.

Thanks,

Tim Young
Elevate Software
www.elevatesoft.com