Creation of Virtual Host

[#1]

Hi,

I wanted to create a virtual host, so I followed the below defined steps:

1. Created a self- signed certificate in apigee keystore request filling up all the necessary informations.

2. Generated a CSR from it, and shared with the signing authority.

3. Received CA signed certificate and updated keystore with the given certificate.

4. Created a DNS entry pointing to CNAME: org-env.apigee.net

5.Created a reference and using management api created the virtual host.

Now on accessing the virtual host name i'm getting error as:

NET::ERR_CERT_COMMON_NAME_INVALID

Subject: *.apigee.net

Issuer: Go Daddy Secure Certificate Authority - G2

Kindly let me know if there is something else to be done.

Thanks.

Regards,

Pratyush

[deboraelkin]

It seems the certificate being presented is the Apigee default one.

1) Please check that the certificate you generated is not issued for Subject: *.apigee.net

2) Check which alias you used when you uploaded the certificate to the keystore

3) Make sure that the vhost configuration is pointing to the correct alias.

[#3]

@deboraelkin,

Thank you for the response. I double checked, points you mentioned are correct at my end.

[pratyush_mohapa]

@Dino,

Could you suggest on my question.

Thanks.

[dchiesa1]

This message:

ERR_CERT_COMMON_NAME_INVALID

Subject: *.apigee.net

...tells me that the cert your peer (client?) is receiving, is the wildcard cert provided by Apigee. It is not YOUR cert.

Check that the API proxy you are creating, actually listens on the new vhost. It should be uniquely named, it should not be the "secure" vhost.

Check that the alias in the vhost is correct, and is not "anything.apigee.net"

Check that you are invoking https://YOUR_DOMAIN_NAME/api/path/here .

[#6 · Accepted solution]

@Pratyush I had this same issue. For me the problem was that I put a period "." in the keystore name. When I recreated the keystore and reference that fixed me up.

[#7]

I hasten to add that having spaces in the virtual host name also breaks things. I think Apigee should do input validation so we can't do these illegal things in their UI.

[dchiesa1]

I wholeheartedly agree. Sorry about that trouble.

[#9]

@Dino-at-Google thank you for confirming.

[pratyush_mohapa]

@Shawn Magill

Might be the issue, will test the same and respond back.

Thank you for the help.