You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sql 2016 reporting would accept a certificate listing e.g. the short form plus the fqdn of a box as alternate subject names, and build bindings for all of them. (Mine also listed a cname short+fqdn).
SSRS 2019 will only bind the principal suject name. Manually adding the missing bindings and mapping them to the same cert in the xml will result in the service not starting.
Workaround: Order one certificate per needed binding - needlessly expensive in terms of maintenance and human error during the next migration... Unless you work on a public CA in which case that translates to actual money.
The text was updated successfully, but these errors were encountered:
Sql 2016 reporting would accept a certificate listing e.g. the short form plus the fqdn of a box as alternate subject names, and build bindings for all of them. (Mine also listed a cname short+fqdn).
SSRS 2019 will only bind the principal suject name. Manually adding the missing bindings and mapping them to the same cert in the xml will result in the service not starting.
Workaround: Order one certificate per needed binding - needlessly expensive in terms of maintenance and human error during the next migration... Unless you work on a public CA in which case that translates to actual money.
The text was updated successfully, but these errors were encountered: