Using logged in user to filter

[John_Titor]

Hi guys!

I Used to have a UX with controls for username and password and in the server side event like in a mobile security situation I would put the following code :

function onLogin as v (e as p)

dim session.UserFirstName as c = ""
dim session.UserLastName as c = ""
dim session.UserUserName as c = ""

if e.loginSucceeded = .T. then 
	dim cn as sql::Connection
	dim args as sql::Arguments
	dim SQL as c
	
'	SQL = "SELECT userid,  Firstname, Lastname FROM websecurityusers WHERE UserName = :UserName"
	args.set("UserName",e.username)
'	if cn.open("::name::ConnectionToExpenseRequests") 
	'	if cn.Execute(SQL,args)
		'	if cn.ResultSet.nextRow() ' a record was found
			'	session.UserFirstName = cn.ResultSet.data("Firstname")
				'session.UserLastName = cn.ResultSet.data("Lastname")
				session.UserUserName = e.username
		'	end if 
		'end if 
		'cn.close()
	end if 
	if session.UserLastName <> ""
		e.userNameFriendly = alltrim(session.UserFirstname)+" "+session.UserLastname 
	end if 

	

end function

Ive started a new project and I created a login component for the web security system a la : https://puu.sh/wdcze.png

So It logs in fine. but I don't know where to put the code to set the logged in user to a session variable. I tried adding it to the on Login page in the UX inserted into the redirected page. But it stays blank.
The HTML page cant have server side events, and the login builder doesn't have anywhere to set server side events.


So my question. When using a Login Builder. How do you set the current logged in user to a session variable?

[Davidk]

Re: Using logged in user to filter

So... you don't want to... or can't... use the UX Integrated Login process?

If not... in your Redirect page - login" UX, in the Server-side onDialogInitialize event, you can use the Context.Security.CurrentUser property to get the current logged in user.

[John_Titor]

Re: Using logged in user to filter

Hey man thanks for the reply. Not sure what you mean by UX integrated login process. Ill try the CurrentUser thing this morning and report back.

[John_Titor]

Re: Using logged in user to filter

C Result = A5ws_GetCurrentUser() in onDialogInitialize.
This worked ! Thanks for pointing me in the right direction.

[Davidk]

Re: Using logged in user to filter

You should be using Context.Security.CurrentUser instead. The Context Object is the current methodology.

[RichCPT]

Re: Using logged in user to filter

Side note: avoid using "DIM" with the "session" pointer variable. Just write:

session.somevar = "Your string value" ' Make sure you only use a string/character value here!!!

Older versions of Alpha did not handle "DIM session.somevar" the way we expected.
https://www.alphasoftware.com/docume...0Variables.xml

[doula]

Re: Using logged in user to filter

Hi David,

Where is the Context.Security.CurrentUser to be found and is there a video or documentation on this?

[iRadiate]

Re: Using logged in user to filter

Hi David,

Where is the Context.Security.CurrentUser to be found and is there a video or documentation on this?

http://downloads.alphasoftware.com/a....html#Security

[Keith Hubert]

Re: Using logged in user to filter

Thanks for info Stephen.

This is helpful to an extent, but I'm still confused as to how the Context.Security.CurrentUser is used in the code posted by John. (Original question).

Please would you mind showing how it is done.

[iRadiate]

Re: Using logged in user to filter

Keith, my reply was to the previous user asking about documentation for the context.security method.

John's original post is setting session variables based on a SQL query. I don't do things this way, I use a login processing page to set any session variables I'm going to need.
But, wherever you used xbasic security functions such as A5ws_GetCurrentUser() has been superseded by the context security methods as David pointed out.

So, for example in server-side xbasic, you could simply do something like:
e.control.Result = "Current Logged-In User = " + Context.Security.CurrentUser

or
dim UserName as c = e.DataSubmitted.User
e.control.Result = UserName + " Belongs To Role: " + Context.Security.GetUserRoles(UserName)

[CharlesParker]

Re: Using logged in user to filter

Does the term superseded mean that getcurrentuser() will eventually be phased out? If so I got a lot of work to do as nearly ALL of my components use this in one way or another. Am I ok to leave them or should I begin making changes now?

[Davidk]

Re: Using logged in user to filter

Not superseded. E.g. A5WS_GetCurrentUser() calls into Context.Security.CurrentUser... so they both end up at the same spot... so no worries. Selwyn is using the A5WS functions in his latest samples... and what's good enough...

I'll tend to use the Context stuff because it's in my head now.

[iRadiate]

Re: Using logged in user to filter

That word superseded is not mine ... it is quoted directly from Alphas' context security object documentation.

"This object supersedes other ways to access web application server context"

Given that, I still use A5WS methods, but I have also started using the context security methods. I will eventually replace the older methods, I just have other priorities at the moment.