[Backlogmanager] [FIWARE-JIRA] (HELP-9284) [fiware-stackoverflow] Fix " Load unsafe scripts" on Map viewer Mashup displaying data from Orion instance

[Fernando Lopez (JIRA)]

     [ https://jira.fiware.org/browse/HELP-9284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Fernando Lopez resolved HELP-9284.
----------------------------------
    Resolution: Done

> [fiware-stackoverflow] Fix "Load unsafe scripts" on Map viewer Mashup displaying data from Orion instance
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: HELP-9284
>                 URL: https://jira.fiware.org/browse/HELP-9284
>             Project: Help-Desk
>          Issue Type: Monitor
>          Components: FIWARE-TECH-HELP
>            Reporter: Backlog Manager
>            Assignee: Álvaro Arranz
>              Labels: fiware, fiware-orion, fiware-wirecloud
>
> Created question in FIWARE Q/A platform on 09-04-2015 at 15:04
> {color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/29540088/fix-load-unsafe-scripts-on-map-viewer-mashup-displaying-data-from-orion-instan
> +Question:+
> Fix "Load unsafe scripts" on Map viewer Mashup displaying data from Orion instance
> +Description:+
> When using Fi-ware map viewer mashup for displaying Points of interest from a orion instance I have to allow ALWAYS "Load unsafe scripts" option on my browser to display them on the map. Otherwise nothing is shown.
> There is a way to configure properly context orion broker or Map viewer mashup? 
> I created a self-signed SSL certificate on the server where Orion runs with the following commands: 
> $ openssl genrsa -des3 -out server.key 1024
> $ openssl req -new -key server.key -out server.csr
> $ openssl x509 -req -days 365 -in server.csr -signkey server.key -out    server.crt
> and I run context Orion broker through https: 
> $contextBroker -https -key <path-to-server-key> cert <path-to-server-cert>
> and then I can make requests through "https" but still having this warning. I guess that it is because my certificate is not a valid one? Maybe I have misconceptions? there is a way to fix it without this workaround? 



--
This message was sent by Atlassian JIRA
(v6.4.1#64016)