more explanation on "a5ws_Login_User"

[Ken Tjia]

I follow the wiki on how to open a a5w pages via xbasic.

i place this codes in the after search... where i confirm
i have valid user id and user password (unencrypted)

variable u and p...

dim pResult as p
pResult = a5ws_Login_User(u,p,"TabbedUI_panel_mobile.a5w")

i expect to see tabbedUI_panel_mobile to open up.

but nothing happen ?

is there something else i need to do ?

appreciate your guidance.

thanks

ken tjia

[Peter.Greulich]

Re: more explanation on "a5ws_Login_User"

Ken,

I don't know, that is kind of a weird function. But the WiKi says this:

Note - once you have a value for RedirectURL, you need to redirect the user, for example:

if return.error = .f.
response.redirect("index.a5w") ' login success page
else
response.redirect("message.a5w") ' login failed message page
end if

Among other things, logically you would expect "false" to mean that the user login was unsuccessful, rather it means that there was no error. Furthermore, you would think that since you are passing in the target page, if the login was successful it would automatically redirect you to that target page, but all it does is populate the system variable, "RedirectURL". Like I said, this is a weird function.

[Steve Wood]

Re: more explanation on "a5ws_Login_User"

Peter, that's exactly how I have it deployed.

Ken, in addition to fomatting it like Peter showed; why are you attempting to do this from an OnSearch event? I expect it logs the person ibut does not do the redirect. You'd have to run a test to see if that is true. I am prettu sure you cannot fire response.redirect() from an OnSearch event and expect a new A5W page to appear. I don't quite understand why you would have an auto-login function running in a search event. What I have done in the past is used a simple dialog with fields for username and password, and feed those values to the function. If they are not found in security, it shoots them to a message page saying so.

[JerryBrightbill]

Re: more explanation on "a5ws_Login_User"

The function only returns a value that CAN be used for a redirect. It does not actually DO the redirect. There was also a bug in the function that caused the "TargetPage" to be ignored with certain security settings. This was fixed in the latest production build 2291.

From the help

Result = A5WS_Login_User()
result.RedirectURL

Successful Login - Will contain the name of the page set as the redirect page after login from the web security configuration. If TargetPage has a value, result.RedirectURL will have the value from TargetPage.

Failed Login - Will contain the name of the page set as the "Redirect page - login" from the web security settings.

The xbasic example given in the help is slightly misleading. While you can set your own redirect target based on the value in Result.error

if return.error = .f.
   response.redirect("index.a5w") ' login success page
else
   response.redirect("message.a5w") ' login failed message page
end if

you can also just use the target automatically to send the user to another page.

response.redirect(result.RedirectURL)

If you don't supply a targetURL, it will return the values set in the security configuration as shown above.

For example,

If you have set the target as in your example:

1. The login failed - result.RedirectURL will contain the name of the page set as the "Redirect page - login" from the web security settings.
2. The login succeded - result.RedirectURL will contain the specified "TargetPage" sent in the function

If you have NOT set the target as in your example:

1. The login failed - result.RedirectURL will contain the name of the page set as the "Redirect page - login" from the web security settings.
2. The login succeded - result.RedirectURL will contain the name of the page set as the redirect page after login from the web security configuration.

[Ken Tjia]

Re: more explanation on "a5ws_Login_User"

Hi Everyone,
yes a good question from Steve... Why i use after search event.

Alpha & many web apps tools speak about going "Mobile".
but the log in dialog that is being provided by Alpha is not usable
for a truth mobile app (my opinion).

In my thought, the user typically holding an iphone straight (portrait)
never mind landscape position. he/she should be able to navigate and log in
to an app.

so i developed a nice keypad of my own, i added a new field in the security database
called, mobile_pin, this typical six digits numeric as a start and i also added a new field
called, password_in_text (kind a unencrypted) , this is where i place user password as
ordinary text (as required by the a5ws_login_user function)

In operation:
User would key in this 6 digits number and perform the search,
naturally it matched the user_id

i constructed a mini a5w page with a keypad, much like a telephone dial pad.
i also place codes to prevent the screen to stretch & scratch ?
this minimize the behaviour of a typical multi touch iphone touch pad.
and allowing this iphone/ipad to behave like a basic touch pad.
with no stretch and all the whistle that we never need.

so keypad is the main mobile login
keypad1 is when user is valid, this iphone button will show
i expect to have 6 choices, iphone, ipad, android pad 7", android pad 8",
android pad 9" & android pad 10", android phone regular & big android phone
like samsung galaxy.

i suppose the liquid form can take care eventually, but such strange behaviour
i decide to manually coded each device.

keypad2, now will open a tabbed_ui, also full of problem.
strange, unexplainable issues, for example

session variable not get passed when i used iphone,
while ipad would pass session perfectly.

this is where i want to apply the a5ws_login....
currently from the iphone button, i pushed to open this tabbedui
ideally, once user is valid, mob1.a5w (the mobile login) would close
and leave tabbedui the only active page.

when tabbedui close/exit, then we fired up the mob1.a5w
to wait for next log in.

in real test on 3G network, perfectly working.
i user "PERFECT BROWSER" app, to give me super speed and FULL SCREEN
feature & locked the display in portrait position.

pardon my English.

hope this explain.

ken tjia

[Ken Tjia]

Re: more explanation on "a5ws_Login_User"

further, i use the scroll feature very well thanks Selwyn.
you notice i use sample of Video 41 to proof the ulink is in fact valid.

this is done on pc browser, if i use it on iphone...
this ulink never get transferred.

i also use video 40 to grab the user's coordinate.
so this would show a user current position etc.

i hope Alpha would consider creating a true mobile log in.
by the way, when i ran this on android pad and any android phone.

the SCROLL GRID, never work.... only showing the first page.
a very frustrating week, trying to do this based on the spirit of

GENIE/DO IT YOURSELF without any code.

sorry to say, it is getting better, but still full of challenge for me.
other more intelligent members can easily fix these issues with few lines
of java or html, but majority of us are just expect to rely on video and
"no code"

[Ken Tjia]

Re: more explanation on "a5ws_Login_User"

Jerry,
thanks for the explanation & let me tried it once more this morning.
i would like to confirm that once the user & password confirmed truth.

this function would triggered and filled the

session.__protected__ulink & would triggered all the necessary
security values ? i found that the redirect pages are being restricted.

i had to temporary set those redirected mobiles pages to "always allowed"
i do believe there is something else i need to run, after reading some replies here & there.

appreciate a better xbasic sample.....

can this be triggered from a basic a5w page with xbasic ?

[Ken Tjia]

Re: more explanation on "a5ws_Login_User"

Ken,

I don't know, that is kind of a weird function. But the WiKi says this:


Among other things, logically you would expect "false" to mean that the user login was unsuccessful, rather it means that there was no error. Furthermore, you would think that since you are passing in the target page, if the login was successful it would automatically redirect you to that target page, but all it does is populate the system variable, "RedirectURL". Like I said, this is a weird function.

hi Steve,
thanks for the comment, yes what you said make sense.
i tried to fired the xbasic a5ws_user_login to open up a a5w page
and just don't see it can....

so i am exploring the DIALOG as you suggested.
now have to learn how to code a keypad..

anyone out there can share such routine ?

[Ken Tjia]

Re: more explanation on "a5ws_Login_User"

hi Steve,
thanks for the comment, yes what you said make sense.
i tried to fired the xbasic a5ws_user_login to open up a a5w page
and just don't see it can....

so i am exploring the DIALOG as you suggested.
now have to learn how to code a keypad..

anyone out there can share such routine ?

Hi Jerry,
I manage to create a brand new mobile login as per Steve's suggestion
this time using Dialog....


submit button has these codes...

dim u as c = "test"
dim p as c = "nnn"

dim pResult as p
pResult = a5ws_Login_User(u,p,"TabbedUI_panel_mobile.a5w")
xbasic_wait_for_idle(3)
response.redirect(pResult.RedirectURL)

see error i got back.....

[Ken Tjia]

Re: more explanation on "a5ws_Login_User"

I am moving along to finalize this mobile login dialog..

i appreciate guidance on how to place dialog's field values to session variable ??

I presume we use "afterdialogvalidate" server side event.
where my mobile pin matched.
the data binding give me perfect name, password, ulink etc..

i would like to know how to populate session variables like:

session.ulink = dialog.ulink field
session.userid = dialog.userid field

i truly can't understand the write up...