EWS RESTful EWS Gateway binding with HTTPS

[Adam_Summers]

Hi,

I'm supporting a customer with securing an endpoint of the EWS Restful Gateway. They have a signed certificate and we are following the notes in the installation guide but seem to be running into some issues. Before I check further I wanted to validate if the correct app id to be binding the certificate with is 596e502c-7957-4a02-8167-716d19ced67f which I have used before to secure the portal.

I wondered if the rest endpoint may come from a different class library and therefore have a different id to bind to.

[sesa180908_brid]

Adam,

The REST endpoints are all spun up from the Mongoose.Service.exe service in a manner that is the same as that of the Portal or a native EWS Server. 

The code for the REST extensions does reside in a different assembly though - (Ews.RestExtensions.dll).

I would have expected those instructions (for the Portal) would also be applicable and work for the REST endpoints.

I'm not familiar with that GUID.  Where did you get it from?

[Adam_Summers]

Hi Mark I took that out of the installation guide P87/88.

I just realised though that we were trying to bind with the local network IP and not 0.0.0.0 which I had done before. Perhaps this was the error so I'm going to check back and will let you know.

netsh http add sslcert ipport=0.0.0.0:8082 certhash= a0f4288e6f511c295362e570dcbf845c0c9247 appid={596e502c-7957-4a02-8167-716d19ced67f} - has that changed in the latest version?

A quick scan of the app id for the assembly Ews.RestExtensions appears to be 7c6feb6c-e1cf-4198-a534-b6b2a1ee9f06 so I may try this too. I recall at least when I build my own Rest Extension as a processor standing up Web.API methods I needed to use the app id of my own assembly and not the SmartConnector server.

[sesa180908_brid]

I don't think we ever changed the Guid of the Service.  But if we did it might have been when we changed the service name (during the 1.3 - 2.0 revision update).  The current GUID for the Service is 0268946a-3985-46f9-a9c2-cd4016ac6ddb.

The one you listed is the one for the Ews.RestExtensions.dll but I would think that the GUID you would use is still the service GUID (above).  Since that's whats actually spinning up the endpoint and hosting it.

[Adam_Summers]

Thanks Mark, will give this a try and report back for future reference in the community. I think that may need a check in the documentation to make sure the correct app guid is listed.

Thanks.

Adam

[SteveGregory]

Did anyone successfully set up a REST Endpoint for EBO that supports HTTPS? We have a project where we need to integrate with a third party over the customers network and they have requested that we use HTTPS. Are there any problems doing this? Is there a step by step guide? I see posts from people who have tried it but not so sure they were successful.