I am not able to get the secure port https for backend url while using Target Servers, with port 443 configured on Apigee Edge UI.

 
Solved Solved
0 2 423
1 ACCEPTED SOLUTION

Choosing a secure port - 443 does not enable the https to backend APIs.

It should be enabled by posting data with parameter SSLInfo using management APIs.

It can not be updated from Apigee Edge UI portal.

Following are the details for enabling the existing target server with https.


curl -X PUT --header "Content-Type: application/json" --header "Authorization: <Basic Auth Value>" -d "{
  \"name\" : \"<target_server_name>\",
  \"host\" : \"<host_name>\",
  \"isEnabled\" : true,
  \"port\" :<port>,
  \"sSLInfo\": {
      \"enabled\": \"true\"
    }
 }" https://api.enterprise.apigee.com/v1/organizations/<org_name>/environments/<env_name>; /targetservers/<target_server_name>

View solution in original post

2 REPLIES 2

Choosing a secure port - 443 does not enable the https to backend APIs.

It should be enabled by posting data with parameter SSLInfo using management APIs.

It can not be updated from Apigee Edge UI portal.

Following are the details for enabling the existing target server with https.


curl -X PUT --header "Content-Type: application/json" --header "Authorization: <Basic Auth Value>" -d "{
  \"name\" : \"<target_server_name>\",
  \"host\" : \"<host_name>\",
  \"isEnabled\" : true,
  \"port\" :<port>,
  \"sSLInfo\": {
      \"enabled\": \"true\"
    }
 }" https://api.enterprise.apigee.com/v1/organizations/<org_name>/environments/<env_name>; /targetservers/<target_server_name>

thanks for the update. We tried that and we think the process is working. We think it might be a validation error. When we look at the curl through the trace tool we see that we are attempting to hit the backend server with http rather than https. We were expecting to see HTTPS. has anybody else seen this?