Setting up Single Sign On

Setting up single sign on is relatively straight forward if you get everything right. If you miss something then trying to figure out what is wrong can prove to be a challenge. Assuming that all three components of SB/XA are configured correctly, these are the pieces that need to be put together. Although the screen shots are all from SB/XA, the same screens are available in both character and GUI.

The prompt Allow local storage of user id's and passwords, can safely be ignored as this feature has not been implemented as yet.

The grid should contain a list of applications that this user has access to and associated operating system and SB/XA user ids if they are different from the main SB/XA user id and Windows Identity entered in the prompt above.

Having completed these steps, save the user security screens and now we can start the client.



After starting the client, as the windows user which you specified in the Windows Identity prompt, you will be presented with the list of applications that you specified in the Single Sign On screen. Select an application and click Connect.



As this is the first time this windows identity is connecting to SB/XA, the U2 Data Server credentials will be requested. These are the operating system credentials required to connect to the server which is hosting the SB/XA application.

Once you have entered the Data Server credentials, you will get a prompt for the SB/XA credentials.



If the user is required to change their password, the Change Password prompt will be shown. Periodically I have had a problem changing the password through SB/XA, if this occurs, connect using SBClient to change the password.



After changing the password - or not - the user will then be connected to the application selected. If you now log off, i.e. /OFF, exit SB/XA and reconnect. Provided everything has been set up as described, you should be prompted for a list of applications and then connected directly to the application.