<div id="header-title" style="padding: 10px 15px; border-width:1px; border-style:solid; border-color:#FFD28C; background-image: url(<nop>https://jazz.net/wiki/pub/Deployment/WebPreferences/TLASE.jpg); background-size: cover; font-size:120%"> ---+!! IBM Quick Deployer WAS single sign on %DKGRAY% %INCLUDE{"IBMQuickDeployerInsertAuthorBuildBasis"}% %ENDCOLOR%</div></sticky> <!-- Page contents top of page on right hand side in box --> <sticky><div style="float:right; border-width:1px; border-style:solid; border-color:#DFDFDF; background-color:#F6F6F6; margin:0 0 15px 15px; padding: 0 15px 0 15px;"> %TOC{title="Page contents"}% </div></sticky> <sticky><div style="margin:15px;"></sticky> 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 [[http://www-01.ibm.com/support/knowledgecenter/SSYMRC_6.0.0/com.ibm.jazz.install.doc/topics/t_deploy_single_sign-on.html?cp=SSYMRC_6.0.0&lang=en][Deploying by using single sign-on authentication]] %INCLUDE{"IBMQuickDeployerInsertMiscellaneous"}% <sticky></div></sticky>
This topic: Deployment
>
WebHome
>
DeploymentInstallingUpgradingAndMigrating
>
IBMQuickDeployerOld
>
IBMQuickDeployerSetupAndRunOld
>
IBMQuickDeployerWASSingleSignOn
History: r10 - 2017-07-28 - 21:45:29 - Main.ktessier
Copyright © by IBM and non-IBM 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
.
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more
here
.