Skip to content

v1.1
Compare
Choose a tag to compare
@Sarafian Sarafian released this 15 Sep 08:00
· 2004 commits to master since this release
stable-1.1
144752e

Release refers to SDL Knowledge Center 2016 SP1 Content Manager 12.0.1 and ISHDeploy.12.0.1.

Summary of release

  • Control internal user authentication when the deployment is integrated with an external security token service (STS)
  • Fine tune Cmdlets
  • Bug fixing
  • Solve previous known issue:

    When the deployment is configured for light weight windows authentication, the described certificate rollover leaves the system broken. The workaround is to re-execute the Set-ISHSTSConfiguration -ISHDeployment $deploymentName -AuthenticationType Windows.

Cmdlets and documentation changes

  1. General
    1. Cmdlets
      • Less warning messages. Warnings are issued when it’s important to share. [Update]
      • Get-ISHDeploymentHistory returns less. Get-* cmdlets are ignored. [Update]
    2. Documentation - Commands
      • Related links render as links and provide a quicker navigation experience. [Update]
  2. Integration STS
    1. Cmdlets
      • Get-ISHDeploymentHistory returns less. Get-* cmdlets are ignored. [Update]
      • Enable-ISHIntegrationSTSInternalAuthentication and Disable-ISHIntegrationSTSInternalAuthentication enable access for internal user authentication. [New]
    2. Documentation - Articles
      • Security Token Service\Integrating with Security Token Service mentions how to enable internal user authentication. [Update]
      • Security Token Service\ADFS\Integrating with Security Token Service mentions how to enable internal user authentication. [Update]
  3. ISHSTS
    1. Cmdlets
      • Set-ISHSTSConfiguration will force the initialization of ISHSTS's database. [Update]
      • Set-ISHSTSConfiguration does check - is Windows Authentication feature installed on environment or not. [Update]
      • Set-ISHSTSRelyingParty parameter -Realm is required to be a proper url with schema. [Update]

Known issues

  • Due to internal dependencies to the product, avoid sequencing first Set-ISHIntegrationSTSCertificate and then Set-ISHSTSConfiguration because they will break the deployment.
Assets 2
Loading