can we merge two workspace into one login page ??

[aal_fareed]

hello everyone ,
i have interesting question for alpha developers ,
lets say you have 3 or 4 workspaces made in alpha ... each one have his own login page ...
my question is .. can we merge all the pages into one single login page .
please share your experience is it possible to achieve that or not ?

[istuart]

Re: can we merge two workspace into one login page ??

An easy way to do it is to link to a navigation page or a tabbedUI after login authentication. I have created simple parent dialog components with many buttons, all of which link to separate components.

[TheSmitchell]

Re: can we merge two workspace into one login page ??

An easy way to do it is to link to a navigation page or a tabbedUI after login authentication. I have created simple parent dialog components with many buttons, all of which link to separate components.

Across multiple, independent workspaces? Or all contained within the same workspace? I think Ahmed wants to have one login for multiple Web applications.

[Mike Reed]

Re: can we merge two workspace into one login page ??

I have a one login page for all users. If the user is an employee they have one menu/tabbed ui system, if the user is a contractor, then a different menu loads or if the user is a customer then a different menu system loads. Is that the kind of thing you are looking to do?

[aal_fareed]

Re: can we merge two workspace into one login page ??

Am trying to let different users who works in different systems
To use login of one page

Its kinda a stage I reached in my company where I had to develop systems seperetly
For individual departments
Then I have to make all this systems into one login page
Ineasted of making a login page for each one
So this is what I need
Make one login access page for different work spaces

Regards

[Mike Reed]

Re: can we merge two workspace into one login page ??

Use the Alpha login system and take advantage of the options that it has built in.
The Alpha security system has all the basic fields you need.
In Web Security Configuration change the setting "login redirect option" to "Page assigned by user profile" as shown in the first figure below.
login1.jpg


The security will need to be tied to one workspace initially, but after it is configured and setup then you can build your web components and pages to access the single security system.
Here is a sample of the new user page I use. The user type noted there actually saves the proper a5w login page to the user tables. Each user type has its own menu system and workspace.

login3.jpg

[aal_fareed]

Re: can we merge two workspace into one login page ??

Use the Alpha login system and take advantage of the options that it has built in.
The Alpha security system has all the basic fields you need.
In Web Security Configuration change the setting "login redirect option" to "Page assigned by user profile" as shown in the first figure below.
[ATTACH=CONFIG]37439[/ATTACH]


The security will need to be tied to one workspace initially, but after it is configured and setup then you can build your web components and pages to access the single security system.
Here is a sample of the new user page I use. The user type noted there actually saves the proper a5w login page to the user tables. Each user type has its own menu system and workspace.

[ATTACH=CONFIG]37441[/ATTACH]

I understand all this ...
But can I make one login page for two different workspace

Yes \ no
That's what I need to know and if yes
Pls share how

For me I think all we have to do is a simple import from the security tables into one MySQL table and set Dbf as active link
To read from MySQL table
And just paste all my users from different workspace
Into MySQL table

Finally copy active link security tables into all your workspaces so when user is made
It will be inserted to MySQL table automaticly isn't that the idea behind active link tables
That's what am trying to find !

[TheSmitchell]

Re: can we merge two workspace into one login page ??

I understand all this ...
But can I make one login page for two different workspace

Yes \ no
That's what I need to know and if yes
Pls share how

For me I think all we have to do is a simple import from the security tables into one MySQL table and set Dbf as active link
To read from MySQL table
And just paste all my users from different workspace
Into MySQL table

Finally copy active link security tables into all your workspaces so when user is made
It will be inserted to MySQL table automaticly isn't that the idea behind active link tables
That's what am trying to find !

We application security is tied to the workspace. You would have to write a bunch of redirects to send their login credentials to the correct web project to log them in. You will have to consider how to handle login invalid, lock outs, landing page after login. This task is easier if your user data is all saved in the same location. Harder if spread out over multiple databases. Probably doable. But, they wouldn't be able to migrate between projects unless you logged them into each web application individually.

[christappan]

Re: can we merge two workspace into one login page ??

Ahmed, if you were to build your own login dialog component rather than using the "login" component, I think you could:
1) Write code in the dialog AfterDialogValidate event to use the entered username and password to query the security tables and determine which workspace that user belongs to
2) Redirect from the dialog component to an a5w page in the applicable workspace and pass the username and password (encrypted) in the url
3) Use the a5ws_login_user() function on the a5w page to log the user in
4) After that function, redirect the user to whatever page the user should start on based on the return values from the a5ws_login_user() function.
It's multiple steps on your end, but would appear seamless to the user.

[aal_fareed]

Re: can we merge two workspace into one login page ??

Ahmed, if you were to build your own login dialog component rather than using the "login" component, I think you could:
1) Write code in the dialog AfterDialogValidate event to use the entered username and password to query the security tables and determine which workspace that user belongs to
2) Redirect from the dialog component to an a5w page in the applicable workspace and pass the username and password (encrypted) in the url
3) Use the a5ws_login_user() function on the a5w page to log the user in
4) After that function, redirect the user to whatever page the user should start on based on the return values from the a5ws_login_user() function.
It's multiple steps on your end, but would appear seamless to the user.

All respect
Thank you sir it's exactly what I was looking for

[Kamel]

Re: can we merge two workspace into one login page ??

Dear Chris,
Thank you for this information, but I have problem with a5_encrypt_string() when I use this funcation it's return different encrypted string comparing with the encrypted password on the websecurity_users as know I use the same Password Encryption Key I saved in the Web Security Configuration,

For example:
In Web Security Configuration I use this Password Encryption Key: "12345678"
And when I create new user for password 123456 the encryption password will be: "ww+6dvcEB9g="
But when I using this funcation:
a5_encrypt_string(e.dataSubmitted.password, "12345678")
The function return this encryption password: "F8R5ftRIg9s="

So please what the wrong ?!?!?

Thanks in advance

Best Regards,
Kamel Jazmati

[christappan]

Re: can we merge two workspace into one login page ??

Kamel, we recently moved our security to SQL so we could have better control (we haven't worked with .dbf so SQL was still the easier route). At this point, when creating users and editing user information, we're bypassing all of the A5 parameters on password length, encryption, etc.

Instead, when we update this information, the password string entered by the user always goes through a function we wrote that encrypts the password before it's saved to the websecurity_users table. Then in the dialog we created, the password string entered by the user goes through the same encryption function before it's used as a variable in the a5ws_login_user() function. Our function actually returns a salted hash that can't be decrypted to reveal the original password string, so it's stronger than the built-in encryption anyway.

passwordHashed = hashPassword(e.dataSubmitted.password)
a5ws_login_user(e.dataSubmitted.userId, passwordHashed)