Does consumer of web service needs to change if the webservice is migrated to https from http?

[Yogesh Gandhi]

I am a web service consumer of a soap web service using a soap client.

Now the web service is going to some other url and also its going on https.

Does client needs to be regenerated? Or it needs any other changes except the change of endpoint url?

Note: The service's internal functionality remains the same, (it is only migrating from http to https and on some different server).
Also it might be going on CLOUD, so there might be a need of PROXY (which earlier was not needed as it was hosted on intranet earlier).

Someone kindly throw some light on this, it'll be a great help.

I have posted the same question on stackoverflow also
https://stackoverflow.com/questions/66157041/does-consumer-of-web-service-needs-to-change-if-the-webservice-is-migrated-to-ht

[Stephan van Hulst]

You shouldn't have to. The URL in a WSDL is usually just a default. You can override the default URL when you construct an instance of the client.

[Yogesh Gandhi]

Stephan van Hulst wrote:You shouldn't have to. The URL in a WSDL is usually just a default. You can override the default URL when you construct an instance of the client.

So that means changing it to https, doesnt require clients to install some sort of certificates or anything? Just changing the endpoint URL is sufficient?

[Tim Holloway]

Yogesh Gandhi wrote:

Stephan van Hulst wrote:You shouldn't have to. The URL in a WSDL is usually just a default. You can override the default URL when you construct an instance of the client.

So that means changing it to https, doesnt require clients to install some sort of certificates or anything? Just changing the endpoint URL is sufficient?

As long as the server's cert is vouched for by a major Certificate Authority, no, no additional client certs are required. The client has been pre-supplied with about 10 or 20 master certs (Verisign, for example), and when a web client wants to confirm the legitimacy of the server's cert, it will chase up the Chain of Trust that links fhe server's cert to one of those pre-installed client master cert.

The master cert list for Java apps is stored in the JRE directory, so every Java app has what it needs to do HTTPS.

[Stephan van Hulst]

If the certificate on the server is signed by an authority that is already trusted by the client, then you don't need to install anything new on the client. If not, then obviously you have to install the certificate in the client's trust store.