Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi,
I know that as a requirement it is necessary that both computers be in the same domain, but I would like to know how the export of certificates works, since this is the main problem, because this client have both servers on AWS with no domain.
When the certificates are exported in Qlik Sense, the FQDN must be set, but for these cases, which are servers without domain, the short name of the server is the same as the FQDN (maybe idk). I think that the message is because that name is not found from outside the network, that is, it is a local name. Should I use the public IP when exporting the certificates?
Regards,
Luis Andrade
Qlik NPrinting Qlik Sense
Hi,
You have answered your question by stating: ".....I know that as a requirement it is necessary that both computers be in the same domain, ....
When the certificates are exported in Qlik Sense, the FQDN must be set, but for these cases, which are servers without domain, the short name of the server is the same as the FQDN (maybe idk). I think that the message is because that name is not found from outside the network, that is, it is a local name. Should I use the public IP when exporting the certificates?...."
Supported solution would require you to create a domain (also in AWS) and put both servers within this domain. What your client has is just not supported and don't expect it to work at all.
Not only that, but also NPrinting service account need to be a domain user belonging to the same domain as both servers - which is another requirement and in your case will not be met... In my opinion it is waste of time trying to get unsupported configuration working. I have been there, I have done that and .... I know it is waste of time as you will run into so many other problems later that will just pile up.
Creating domain obviously should be thought about before everything was installed.. In this case you can play with IPs etc... but at the end it is still not supported. You will have issues like: reports running ok one day, and not running another day, You will not be able to configure OnDemand nor use API properly... you may have issues with connections.. list can go long...
Obviously there is nothing stopping you from trying to run unsupported configuration, but then dont expect to have documentation on that, right? My answer seem to be little off the topic, but I hope you understand that this is not how NPrinting works, hence no point talking about ip addresses used as certificates host names... also remember that when exporting certificates you are actually putting NPrinitng host name as FQDN....https://help.qlik.com/en-US/nprinting/November2020/Content/NPrinting/DeployingQVNprinting/NPrinting-...
My advice is:
The above will save you a lot of time and trouble in the future as supporting unsupported configuration is not really possible - you have no Qlik support then and you are on your own...
Hi,
You have answered your question by stating: ".....I know that as a requirement it is necessary that both computers be in the same domain, ....
When the certificates are exported in Qlik Sense, the FQDN must be set, but for these cases, which are servers without domain, the short name of the server is the same as the FQDN (maybe idk). I think that the message is because that name is not found from outside the network, that is, it is a local name. Should I use the public IP when exporting the certificates?...."
Supported solution would require you to create a domain (also in AWS) and put both servers within this domain. What your client has is just not supported and don't expect it to work at all.
Not only that, but also NPrinting service account need to be a domain user belonging to the same domain as both servers - which is another requirement and in your case will not be met... In my opinion it is waste of time trying to get unsupported configuration working. I have been there, I have done that and .... I know it is waste of time as you will run into so many other problems later that will just pile up.
Creating domain obviously should be thought about before everything was installed.. In this case you can play with IPs etc... but at the end it is still not supported. You will have issues like: reports running ok one day, and not running another day, You will not be able to configure OnDemand nor use API properly... you may have issues with connections.. list can go long...
Obviously there is nothing stopping you from trying to run unsupported configuration, but then dont expect to have documentation on that, right? My answer seem to be little off the topic, but I hope you understand that this is not how NPrinting works, hence no point talking about ip addresses used as certificates host names... also remember that when exporting certificates you are actually putting NPrinitng host name as FQDN....https://help.qlik.com/en-US/nprinting/November2020/Content/NPrinting/DeployingQVNprinting/NPrinting-...
My advice is:
The above will save you a lot of time and trouble in the future as supporting unsupported configuration is not really possible - you have no Qlik support then and you are on your own...
Hi Lech,
I know the requirements, but this customer had Qlik Sense first, which I understand does not need to have a domain. They are recently migrating your NPrinting server to AWS. The customer is already aware that they must create a domain and they going to do that soon.
My question is about how the certificates that are exported from Qlik Sense works. Why is the FQDN used when exporting certificates? and Why is the short name used when installing the Engine?
Thanks in advance.
That I am not sure of and it is not really documented anywhere..
This is only guess but I think it may be Qlik Sense requirement for communication/authentication to have FQDN (just like you need certificates when opening hub in browser to avoid cert errors...) For the engine - I only guess it is internal to NPrinting, hence not required.
Hi,
I think that this detail is not documented. In any case it is mandatory to fill the documented requirements because other configurations could not work. As general rule we document all and only the supported configurations. Other, not documented, configurations could work but we do not support them.
Best Regards,
Ruggero
Hi,
My question is about how the certificates that are exported from Qlik Sense works. Why is the FQDN used when exporting certificates? and Why is the short name used when installing the Engine?
This is what I need to do in a default configuration.
The problem with the domains will be remedy soon.
Regards,
Luis Andrade
Hi,
It is a Qlik Sense requirement. I asked why, if I will found an answer I will add it here.
Best Regards,
Ruggero