Notifications
Announcements
No record found.
Hi all,
I want to install "Report Server" on "HTTPS".
We want to secure our report server with SSL certificate.
Can anyone guide me how to do this?
*This post is locked for comments
Create or pick a certificate that is trusted by your client machines, or you'll be forced to install the certificate on the clients to establish trust, which could be a lot of effort. If you have a domain CA, your client machines will trust the certificate automatically. There are plenty of good step by step technet articles on creating a certificate from a domain CA. Make sure your certificate supports both the fully qualified domain name (FQDN) and any alternate DNS for the machine.
Once the certificate is installed on the SSRS server, use the SQL Server Reporting Service Configuration Manager to add a new Web Service URL and Report Manager URL, using https:// instead of http:// for both.
Then in your Report servers configuration in Dynamics AX, change the Report Manager URL and Web service URL to use https:// instead of http:// for both.
Hi Brandon,
Thanks for reply.
I have successfully created Self signed Certificate and added Web Service & Report manager URL.
It is accessible if we use full link >>> https://ComputerName.Domain:Port/ReportServer
But its not accessible if we open it with IP >>> https://ComputerIP:Port/ReportServer
What can be the issue?
The certificate in this case is not just providing the necessary key material for encryption, but also proof of identity. If you use the IP address in the URL, but the certificate only provides identity for the server by its fully qualified DNS name, then those aren't the same thing, and identity is not established. That's why I said to include all of the alternate DNS names when creating your certificate, i.e. all of the other ways that you connect to your server in the URL.
Thanks for quick response.
Can you please tell me how to include alternative DNS names in certificate?
It depends on the tool that you used to create the CSR. There should be a place to provide alternate subject names. If you intend to use the IP address, you may have to add the IP address both as type DNS and as type IP address, as some web clients do not validate correctly when the IP address type is used. Do not try to use multiple subject names.
I don't think I've ever created a certificate for an IP address. Consider using DNS for what it was designed to do, which is to abstract identity from the underlying network structure.
Thanks again for the response.
I have created a Self Signed Certificate and it does not have "Subject Alternative Name".
Even when I am creating Self Signed Certificate, it does not ask me any settings except certificate's name.
Any solution to provide "Subject alternative name" in Self signed certificate?
Again, I don't know what tool you're using to create the certificate.
Consider using a domain CA. The certificate enrollment tool provides for alternate subject names, and the domain certificate will be trusted by domain clients automatically.
But, in general it's not a best practice to use IP addresses in your certificates, as they can change quite easily whereas the name of the machine can be quite a bit more stable.
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Martin Dráb 4 Most Valuable Professional
Priya_K 4
MyDynamicsNAV 2
