Subject Alternate Name

[randyt]

It appears that our upgraded Veeam B&R server has a new certificate that is causing communication problems when using the API. I had worked with the API earlier this year (before the upgrade) and was able to interact with Veeam using API calls. The old certificate has a CN that lists the FQDN of the Veeam server. The CN field in the new cert looks like this:

CN=Veeam Backup Server Certificate

I think the client doesn't know what to do with this. This isn't my area of expertise but from what I've read, if the cert had a Subject Alternate Name included (with something meaningful to the API client), this would fix the problem.

Q1 - does the Veeam admin have the ability to generate a new cert with a S.A.N.?

Q2 - if not, how do I resolve this?

Q3 - can I force Veeam to use the old cert?

Thanks!

[Mildur]

Hello Randyt

I believe this is a known issue.
Could you maybe open a case with our customer support so we can confirm it?

Thanks,
Fabian