r10 - 2017-07-28 - 21:45:29 - Main.ktessierYou are here: TWiki > 
Deployment Web > DeploymentInstallingUpgradingAndMigrating > IBMQuickDeployerOld > IBMQuickDeployerSetupAndRunOld > IBMQuickDeployerWASSingleSignOn
Deployment Web > DeploymentInstallingUpgradingAndMigrating > IBMQuickDeployerOld > IBMQuickDeployerSetupAndRunOld > IBMQuickDeployerWASSingleSignOn IBM Quick Deployer WAS single sign on 
Authors: ThomasPiccoli, KennethThomson, JenniferLiu, KenTessier, ClareCartyBuild basis: CLM 6.0, CLM 6.0.x, CE 6.0.x
Page contents
From Quick Deployer v1.1 WAS single sign on (SSO) has been automated.
Quick Deployer v1.0 does not implement WAS single sign on (SSO), this means that if you have deployed your applications across a distributed system you will continually be prompted to authenticate as you move from one application to another. This topic shows how this can be avoided by manually configuring WAS SSO after running the Install Applications process.
Quick Deployer WAS single sign on
To configure your QD system for WAS single sign on follow the instructions contained in section Deploying SSO on WebSphere Application Server of Deploying by using single sign-on authenticationMiscellaneous
Notes:
- Throughout the IBM Quick Deployer wiki the screen captures are for reference only.
In some cases if the functionality they display has not changed in the latest release they will be from a previous release
Related topics:
External links:
Additional contributors: MichelleCrane, NathanBak, ChristianLopez
-
Deployment web
-
Planning and design
- Installing and upgrading
- Migrating and evolving
- Integrating
- Administering
- Monitoring
- Troubleshooting
- ELM SaaS
Community information and contribution guidelines 
Topic list 
Search 
Advanced search 
Notify 
RSS 
Atom 
Changes 
Statistics 
Web preferences 
NOTE: Please use the Sandbox web for testing -
To do
-
Under construction
-
New
- Updated
-
Constant change
- None - stable page
- Smaller versions of status icons for inline text:
-
Copyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors. Contributions are governed by our Terms of Use. Please read the following disclaimer.