Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Sep 2, 2022 9:20:46 AM
Dec 8, 2020 3:51:11 AM
IMPORTANT NOTE: The following steps are applicable for Qlik Sense multi-node and Multi-cloud deployments using app distribution that have been upgraded to September 2020 release (or later) from versions prior to the September 2020 release.
This does not apply to:
For those three, follow the standard Upgrade Instructions (Source: Qlik Help).
Note that if you have a single node deployment that uses app distribution, you have one additional step to perform after following standard upgrade instructions. You will be required to recreate the identity provider in QCS tenant for QSEfW setup. This is required because the local bearer token for cloud deployment is recreated using a new certificate after QSEfW has been upgraded to September 2020 release or later.
Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass
function RemoveCertificatesFromStore(
[string] $name,
[string] $location)
{
$success = 1
$oid = "1.3.6.1.5.5.7.13.3"
$localStore = new-object System.Security.Cryptography.X509Certificates.X509Store $name, $location
$localStore.Open("MaxAllowed")
try
{
$certs = $localStore.Certificates
foreach ($cert in $certs)
{
$extensions = $cert.Extensions
foreach($extension in $extensions)
{
if ($extension.Oid.Value.Equals($oid))
{
write-host "Deleting certificate from" $localStore.Name $localStore.Location
write-host " Subject:"$cert.Subject
write-host " Issuer:"$cert.Issuer
write-host " Serial:"$cert.SerialNumber
$localStore.Remove($cert)
break;
}
}
}
}
catch
{
write-host "An error occurred while removing certificates" -ForegroundColor Red
write-host $_.Exception.GetType().FullName -ForegroundColor Red
write-host $_.Exception.Message -ForegroundColor Red
$success = 0
}
finally
{
$localStore.Close()
}
if ($success -ne 1)
{
exit 20
}
}
function CleanCertificates()
{
RemoveCertificatesFromStore "Root" "LocalMachine"
RemoveCertificatesFromStore "My" "LocalMachine"
RemoveCertificatesFromStore "My" "CurrentUser"
}
CleanCertificates
write-host "Done."
exit 0
@Sonja_Bauernfeind is this a notice about the coming 2020 Sep release?
@AdamBSnotused Correct!
Sooo ... all you need to do in single node + SaaS environment is delete and recreate the identity provider?
Article does not (yet) clearly mention this ...
Hello @john_oll I'm looking at getting you an answer for this. Will get back to you ASAP and then update the article accordingly.
In my single node I see my one historical success
But in multi-cloud setup, the deployments page issues the error:
All I can see in support portal is that the user must have rootadmin or deployadmin, but I have attempted with the administrative account and the installing rootadmin user. Looking forward to anything you dig up Sonja. Must apologise, I have not registered my problem with support.
Hello @AdamBSnotused - I think your issue might require more investigation than I can assist with here. I'd recommend taking this to the appropriate forum on here to engage with our userbase: Qlik Senes SaaS & Multi-Cloud.
Hello @john_oll
As per our Subject Matter Experts:
This does not apply to:
For those three, follow the standard Upgrade Instructions (Source: Qlik Help).
So, for a Single Node you will not have to follow any of the steps listed in this article - as they only apply to Multi-Node installations.
Hello @Sonja_Bauernfeind ,
I have to disagree,
I made an upgrade for "Qlik Sense Single Node deployments using app distribution to Qlik Sense SaaS" , and this broke the app distribution to SaaS.
And applying the fix (deleting, recreating Identity provider) fixed it!
Notice that this probably happened since the Server had no SSL certificate, so the installation automatically removed and restored the certificate during the update.
But this problem and this solution does affect "Qlik Sense Single Node deployments using app distribution to Qlik Sense SaaS"!
Let me get back in touch with our SMEs, @john_oll! Thanks for bringing this here though, really appreciate it.
We've updated the article based on feedback from our developer, @john_oll .
What was added:
Note that if you have a single node deployment that uses app distribution, you have one additional step to perform after following standard upgrade instructions. You will be required to recreate the identity provider in QCS tenant for QSEfW setup. This is required because the local bearer token for cloud deployment is recreated using a new certificate after QSEfW has been upgraded to September 2020 release or later.