I have an iwp db solution whereby I want the "guest" (data entry only) (set up in accounts and privs) to not be able to edit any records other than the one that opens when they access the url. I have the status area hidden and locked ... I want others (defined in accounts with full access) to hit a button and login and make editing changes. My script for re-login (or enable account) doesn't bring up a request for user id and password, which is what I want. Can anyone please help me with the script that allows 'everyone' to enter the db with limited priviledges, then with authentication, allow select people with user id and password then to access all records with full priviledges.

I have an iwp db solution whereby I want the "guest" (data entry only) (set up in accounts and privs) to not be able to edit any records other than the one that opens when they access the url. I have the status area hidden and locked ... I want others (defined in accounts with full access) to hit a button and login and make editing changes. My script for re-login (or enable account) doesn't bring up a request for user id and password, which is what I want. Can anyone please help me with the script that allows 'everyone' to enter the db with limited priviledges, then with authentication, allow select people with user id and password then to access all records with full priviledges.

I have an iwp db solution whereby I want the "guest" (data entry only) (set up in accounts and privs) to not be able to edit any records other than the one that opens when they access the url. I have the status area hidden and locked ... I want others (defined in accounts with full access) to hit a button and login and make editing changes. My script for re-login (or enable account) doesn't bring up a request for user id and password, which is what I want. Can anyone please help me with the script that allows 'everyone' to enter the db with limited priviledges, then with authentication, allow select people with user id and password then to access all records with full priviledges.

I'm trying to work through the exact same issue. I'm thinking this might be a possibility:

Create two entry point links. The first would be for guest access (ie - http://www.mydomain.com/fmi/iwp/cgi?-db=mydb&-startsession). From there the re-log script would do its thing. The second link would be for admin access (ie - http://www.mydomain.com/fmi/iwp/cgi?-db=mydb&-syntax-to-prompt-for-login).

I'm pretty sure you could do something like this with a CWP solution and XML. But I'm not sure if IWP is going to carry the same weight.

I'm trying to work through the exact same issue. I'm thinking this might be a possibility:

Create two entry point links. The first would be for guest access (ie - http://www.mydomain.com/fmi/iwp/cgi?-db=mydb&-startsession). From there the re-log script would do its thing. The second link would be for admin access (ie - http://www.mydomain.com/fmi/iwp/cgi?-db=mydb&-syntax-to-prompt-for-login).

I'm pretty sure you could do something like this with a CWP solution and XML. But I'm not sure if IWP is going to carry the same weight.

I'm trying to work through the exact same issue. I'm thinking this might be a possibility:

Create two entry point links. The first would be for guest access (ie - http://www.mydomain.com/fmi/iwp/cgi?-db=mydb&-startsession). From there the re-log script would do its thing. The second link would be for admin access (ie - http://www.mydomain.com/fmi/iwp/cgi?-db=mydb&-syntax-to-prompt-for-login).

I'm pretty sure you could do something like this with a CWP solution and XML. But I'm not sure if IWP is going to carry the same weight.

Cranes,

See if this helps you out. It worked for our requirements.

Create a button with a login script, a user name text box and a password text box. The password won't be encrypted when it's typed in though. You'll also need a script to clear the login text boxes. I've included where I placed that script below.

Script for button...

If [dbname::admin_login_name = "admin" and wtcconf::admin_login_pwrd = "password"] - (not very secure to have a password in a script I guess, but it works for us.)

Perform Script [Clear Fields] - (This script clears the login fields and returns the cursor to the admin name text box... otherwise login credentials will remain in the text boxes when someone comes back to the page)

Show/Hide Status Area [Lock; Show] - (unlocks status area)

Go to Layout [Your admin layout]

Re-login [No dialog]

Else

Perform Script [Clear Fields]

Go to Layout [Error layout] - (login credentials failed)

End If

Hope this helps!!!

another solution is to disable the account called "[guest]" and create a read-only account called "guest" with no password. It will then prompt everyone for the password and guests just type "guest" as the username.

Similar issue here: I want the general public to be able to access IWP without providing a username (or, even typing "guest"), but other users to be able to log in and provide username/password for additional access.

Is there a way to specify the account name (but not password) in the URL?