05-21-2018 10:49 PM - edited 05-22-2018 02:51 PM
I understood that for some browsers (e.g. Chrome), Locate me only works with HTTPS.
However a HTTPS Consumer Portal instance doesn't have a working WMPS search - as WMPS service is only available via HTTP.
So seems that we are stuck here: if we want to have locate me tool working, the search will fail, if we want to have WMPS search working, the locate me will fail.
Is there a way to get WMPS working as HTTPs in Consumer Portal?
Solved! Go to Solution.
05-24-2018 01:37 AM - edited 05-24-2018 01:37 AM
I replied to Yuan through the support ticket logged.
For others, please check the updated article my latest comment here:
05-27-2018 04:59 PM
Thanks for your comments, I have replied in the ticket.
Basically the solution you provided works, we could now use the HTTPs Backend Search service in a HTTPS enabled Consumer Portal site.
However the search pins don't display for the returned search results, did you manage it to get it working in your instance?
06-05-2018 03:56 AM
I see the same behavior on my test bed. By checking the Developer Console, I could see that the PUT request to BackendWMPS returns error. Looks like another binding issue. I haven't been able to find the proper settings thus I attached the ticket to existing 'WMPS vs. HTTPS' entry in development's backlog.