Multiple Business Spaces

bpolak

Does anyone know if it's possible for a user to log on to two business spaces at the same time?

aware_support

Doing it on the same machine is not recommended - it may cause different weird errors. Logging in from different machines shouldn't be a problem.

RocketRod

Gee this is going to be a real problem for us. We are just about to go live with several BS's we have been testing and now I have to tell my users that they have to log out and in to each BS all day. They wont be happy. Will this be addressed in the future? Also I'm sure some of them will forget. Will it cause any data integrity issues?

tford

RocketRod,

FYI -- You can run 1 BS from another.

Tom

RocketRod

Thanks Tom, so I could build a BS that was just a menu front end to a number of other BS's? How do I do it? I can't see any relevant menu option when setting up a perspective? And are you therefore saying that they can have more than one of these BS's open at anyone time?

Cheers Rod

aware_support

This will not cause data integrity issues, but a server may confuse requests coming from different sessions in the same browser. This is not the Aware IM problem - it s a general problem with all web applications that use cookies to distinguish between sessions.

I believe this issue has already been discussed on this forum several times.

You do need to manage this within one application or ask users to logout and login.

You may choose to ignore the issue and if you are lucky you may get away with it.

RocketRod

Thanks Support. I just need to know how to manage several BS's from within one BS. Is there another topic that describes this or can someone tell me please.

tford

And are you therefore saying that they can have more than one of these BS's open at anyone time?

No, I was thinking that you could have multiple menu items of type Logout. Each one could point to a different BS's URL-- for example:
http://xyz.com:8080/AwareIM/logonOp.aw?domain=BSname

That would take you to a login screen for BSname.

I know that may not be optimal, but it might save a step.

Tom

christopherb

I don't know your application or your user infastructure but as Tom mentioned you could call each BS from the set of link(s) on a menu.

Then for user coming into application "fresh" create a HTML login screen with appropriate link(s) to an BS they wish to access. This will allow you control the broswer window also to hide menus, backbutton and such. But like i said i dont know you application.

Good luck....

RocketRod

For interest sake, just a post to let others know what I have done to overcome this issue. I will have many BS's for my users so I needed a solution that would control the access and force them to use one BS at a time.

I created a main BS that has a menu structure of which each item calls another BS. The menu item is of the logout type with the url of the login for the required BS. This main BS uses the same password for each user so I just use the full parametised logon, therefore no logging on for each user. I grab the username from my system.
When a user clicks on a menu item they are prompted for the username and password for the BS. When they logout of the sub BS it returns them to the main BS by using the URL again. Remember password is common for all users so full parametised password logon to the main BS can be used again.
To overcome users having to change passwords in each BS I did the following to achieve a common password for them. In the main BS I added the regularuser table for each sub BS as an existing external. Then I added a new BO to hold the password for each user , added it to the systemuser group so that it added the accesslevel, password and loginname fields and then removed it from the systemuser group but said no to do you want to remove the fields.
I then set up a process to use the loginname of the logged in user to find the appropriate instance of the above BO and then have them change the password.
Finally I set up rules on the BO one for each sub BS, that is one for each existing external BO that I had added, to find the appropriate instance and set its password to the changed password on this BO.

So summing up:

I have one controlling BS which users do not need a password to log on to.
When they change the password in this BS it changes the password for them across all their BS's so they only have to remember one password and do it once. I will tell them to use their network password.
It forces them to logout then into a new BS so they can only ever be in one BS at a time.
Easy for me to maintain for as I write a new BS I just need to add its password table as an existing external to the main BS and set up its rule.
Users like it as its quick and easy to move between BS's and they only need one password.

Hope I explained it ok.

Cheers

tford

Rod,

Very creative !!

Thanks very much for sharing!

Tom