I've created a very simple first EWB app connecting to a EDB database, i'm learning every step of the way.

I want to create an authentication screen which asks for the database username and password on each visit and sets the database.username password properties accordingly.

On successful sign in I would show the user the second screen which allow viewing and editing a simple data form.

Is there a way to check is the username and password is correct so I can inform the user and not proceed the the second screen. At the moment if I enter an incorrect password a Windows authentication dialog appears on the PC running the EWB server prompting for username and password and not the web client.

What would be the best way to authenticate users logging in to a EWB application with an EDB back end database?

I'm looking for a solution to this as I've not been able to get it working myself.

Many thanks

Anthony wrote:

> What would be the best way to authenticate users logging in to a EWB
> application with an EDB back end database?
>
> I'm looking for a solution to this as I've not been able to get it
> working myself.

My understanding from reading previous posts here is that EWB's server
has a header that you pass in for authentication. To use it, you'd
create a login form or panel, and then use the values entered to pass
in. I guess you could do a simple query to test the credentials. EWB's
security seems sensible if you set it up properly.

There is of course the usual "should I put a database straight onto the
internet" question - the alternative being to have an interface made of
functions that you call, and the database and business logic are hidden
behind that. But for intranet stuff, direct database is probably fine.


--

Matthew Jones

Hi Matthew, thanks for your reply

Yes I have what you describe, my problem is that if I enter incorrect credentials on the initial form, a windows dialog box appears on the PC with the EDB server running for each incorrect login and I haven't been able to find a way to trap this within the EWB application.

>"Matthew Jones" wrote:
>
>My understanding from reading previous posts here is that EWB's server
>has a header that you pass in for authentication. To use it, you'd
>create a login form or panel, and then use the values entered to pass
>in. I guess you could do a simple query to test the credentials. EWB's
>security seems sensible if you set it up properly.

I have purposely left the username and password blank in the EWB dataset manager so each user has to enter their own username and password on the EWB authentication form and not allowing access to the database without authentication. Am I missing some other way of querying a valid username and password?

>There is of course the usual "should I put a database straight onto the
>internet" question - the alternative being to have an interface made of
>functions that you call, and the database and business logic are hidden
>behind that. But for intranet stuff, direct database is probably fine.

I was hoping to only use the Elevate tools to achieve this, is this possible or would I need some other tool to create the middle ware interface?

Anthony wrote:

> Yes I have what you describe, my problem is that if I enter incorrect
> credentials on the initial form, a windows dialog box appears on the
> PC with the EDB server running for each incorrect login and I haven't
> been able to find a way to trap this within the EWB application.


Raise a support issue for this (and post the response here if
possible). I expect there will be a solution that Tim has.


--

Matthew Jones

Anthony wrote:

> I have purposely left the username and password blank in the EWB
> dataset manager so each user has to enter their own username and
> password on the EWB authentication form and not allowing access to
> the database without authentication. Am I missing some other way of
> querying a valid username and password?

As you have probably seen, EWB 1.04 is now out with a fix for this
issue.

--

Matthew Jones

Yes, just downloaded and tested and now working, thanks

"Matthew Jones" wrote:

Anthony wrote:

> I have purposely left the username and password blank in the EWB
> dataset manager so each user has to enter their own username and
> password on the EWB authentication form and not allowing access to
> the database without authentication. Am I missing some other way of
> querying a valid username and password?

As you have probably seen, EWB 1.04 is now out with a fix for this
issue.

--

Matthew Jones