Details
-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:
-
Story Points:5
-
Epic Link:
-
Sprint:Summer 4: 14 Jul - 28 Jul, Summer 5: 3 Aug - 14 Aug, Summer 6: 17 Aug - 28 Aug
Description
Making requests to the IGB API is done over http and some browsers see a security issue with doing so under an overarching secured connection and classify this as Mixed Content. Safari, for instance, blocks these sorts of requests.
Instead of making requests in this way, the window location can be changed using javascript, which initializes a new connection, circumventing the error. See my comment here for more details.
Task: Update the requests in app store to use the method described above, in order to allow all browsers to interact with IGB.
Update: Allow browsers that do not support http connections to localhost on a secure parent connection to connect to IGB over https.
Attachments
Issue Links
- relates to
-
-
- Closed
-
-
IGBF-2505 Turn off redirection to https for galaxy bridge in bioviz-playbooks
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
Activity
| Field | Original Value | New Value |
|---|---|---|
| Epic Link | IGBF-1388 [ 17463 ] |
| Status | To-Do [ 10305 ] | In Progress [ 3 ] |
| Status | In Progress [ 3 ] | Needs 1st Level Review [ 10005 ] |
| Summary | Fix implementation of requests to IGB endpoints to support safari etc. | Investigate: Fix implementation of requests to IGB endpoints to support safari etc. |
| Assignee | Philip Badzuh [ pbadzuh ] |
| Status | Needs 1st Level Review [ 10005 ] | First Level Review in Progress [ 10301 ] |
| Status | First Level Review in Progress [ 10301 ] | To-Do [ 10305 ] |
| Assignee | Philip Badzuh [ pbadzuh ] |
| Status | To-Do [ 10305 ] | In Progress [ 3 ] |
| Sprint | Summer 4: 14 Jul - 28 Jul [ 99 ] | Summer 4: 14 Jul - 28 Jul, Summer 5: 29 Jul - 12 Aug [ 99, 100 ] |
| Rank | Ranked higher |
| Story Points | 1 | 5 |
| Description |
Making requests to the IGB API is done over https and some browsers see a security issue with doing so under an overarching secured connection and classify this as Mixed Content. Safari, for instance, blocks these sorts of requests.
Instead of making requests in this way, the window location can be changed using javascript, which initializes a new connection, circumventing the error. See my comment [here|https://jira.transvar.org/browse/IGBF-2420?focusedCommentId=28555&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-28555] for more details. Task: Update the requests in app store to use the method described above, in order to allow all browsers to interact with IGB. |
Making requests to the IGB API is done over https and some browsers see a security issue with doing so under an overarching secured connection and classify this as Mixed Content. Safari, for instance, blocks these sorts of requests.
Instead of making requests in this way, the window location can be changed using javascript, which initializes a new connection, circumventing the error. See my comment [here|https://jira.transvar.org/browse/IGBF-2420?focusedCommentId=28555&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-28555] for more details. Task: Update the requests in app store to use the method described above, in order to allow all browsers to interact with IGB. Update: Allow browsers that do not support http connections to localhost to connect to IGB over https. |
| Status | In Progress [ 3 ] | Needs 1st Level Review [ 10005 ] |
| Assignee | Philip Badzuh [ pbadzuh ] |
| Description |
Making requests to the IGB API is done over https and some browsers see a security issue with doing so under an overarching secured connection and classify this as Mixed Content. Safari, for instance, blocks these sorts of requests.
Instead of making requests in this way, the window location can be changed using javascript, which initializes a new connection, circumventing the error. See my comment [here|https://jira.transvar.org/browse/IGBF-2420?focusedCommentId=28555&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-28555] for more details. Task: Update the requests in app store to use the method described above, in order to allow all browsers to interact with IGB. Update: Allow browsers that do not support http connections to localhost to connect to IGB over https. |
Making requests to the IGB API is done over https and some browsers see a security issue with doing so under an overarching secured connection and classify this as Mixed Content. Safari, for instance, blocks these sorts of requests. Instead of making requests in this way, the window location can be changed using javascript, which initializes a new connection, circumventing the error. See my comment [here|https://jira.transvar.org/browse/IGBF-2420?focusedCommentId=28555&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-28555] for more details. Task: Update the requests in app store to use the method described above, in order to allow all browsers to interact with IGB. Update: Allow browsers that do not support http connections to localhost on a secure parent connection to connect to IGB over https. |
| Description |
Making requests to the IGB API is done over https and some browsers see a security issue with doing so under an overarching secured connection and classify this as Mixed Content. Safari, for instance, blocks these sorts of requests. Instead of making requests in this way, the window location can be changed using javascript, which initializes a new connection, circumventing the error. See my comment [here|https://jira.transvar.org/browse/IGBF-2420?focusedCommentId=28555&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-28555] for more details. Task: Update the requests in app store to use the method described above, in order to allow all browsers to interact with IGB. Update: Allow browsers that do not support http connections to localhost on a secure parent connection to connect to IGB over https. |
Making requests to the IGB API is done over http and some browsers see a security issue with doing so under an overarching secured connection and classify this as Mixed Content. Safari, for instance, blocks these sorts of requests. Instead of making requests in this way, the window location can be changed using javascript, which initializes a new connection, circumventing the error. See my comment [here|https://jira.transvar.org/browse/IGBF-2420?focusedCommentId=28555&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-28555] for more details. Task: Update the requests in app store to use the method described above, in order to allow all browsers to interact with IGB. Update: Allow browsers that do not support http connections to localhost on a secure parent connection to connect to IGB over https. |
| Status | Needs 1st Level Review [ 10005 ] | First Level Review in Progress [ 10301 ] |
| Assignee | Ann Loraine [ aloraine ] |
| Status | First Level Review in Progress [ 10301 ] | To-Do [ 10305 ] |
| Assignee | Ann Loraine [ aloraine ] | Philip Badzuh [ pbadzuh ] |
| Rank | Ranked higher |
| Status | To-Do [ 10305 ] | In Progress [ 3 ] |
| Attachment | igb-client-https.png [ 14814 ] |
| Status | In Progress [ 3 ] | Needs 1st Level Review [ 10005 ] |
| Assignee | Philip Badzuh [ pbadzuh ] |
| Fix Version/s | 9.1.0 Major Release [ 10601 ] | |
| Labels | Advanced |
| Status | Needs 1st Level Review [ 10005 ] | First Level Review in Progress [ 10301 ] |
| Status | First Level Review in Progress [ 10301 ] | To-Do [ 10305 ] |
| Assignee | Philip Badzuh [ pbadzuh ] |
| Status | To-Do [ 10305 ] | In Progress [ 3 ] |
| Attachment | igb-browser-https-v2.png [ 14818 ] |
| Assignee | Philip Badzuh [ pbadzuh ] |
| Status | In Progress [ 3 ] | Needs 1st Level Review [ 10005 ] |
| Status | Needs 1st Level Review [ 10005 ] | First Level Review in Progress [ 10301 ] |
| Status | First Level Review in Progress [ 10301 ] | To-Do [ 10305 ] |
| Assignee | Philip Badzuh [ pbadzuh ] |
| Status | To-Do [ 10305 ] | In Progress [ 3 ] |
| Attachment | browser-communication-with-igb-api-v3.png [ 14831 ] |
| Status | In Progress [ 3 ] | Needs 1st Level Review [ 10005 ] |
| Assignee | Philip Badzuh [ pbadzuh ] |
| Sprint | Summer 4: 14 Jul - 28 Jul, Summer 5: 3 Aug - 14 Aug [ 99, 100 ] | Summer 4: 14 Jul - 28 Jul, Summer 5: 3 Aug - 14 Aug, Summer 6: 17 Aug - 28 Aug [ 99, 100, 101 ] |
| Rank | Ranked higher |
| Status | Needs 1st Level Review [ 10005 ] | First Level Review in Progress [ 10301 ] |
| Assignee | Philip Badzuh [ pbadzuh ] |
| Status | First Level Review in Progress [ 10301 ] | To-Do [ 10305 ] |
| Status | To-Do [ 10305 ] | In Progress [ 3 ] |
| Attachment | browser-communication-with-igb-api-v3.png [ 14831 ] |
| Attachment | igb-browser-https-v2.png [ 14818 ] |
| Attachment | igb-client-https.png [ 14814 ] |
| Attachment | browser-igb-communication.png [ 14838 ] |
| Status | In Progress [ 3 ] | Needs 1st Level Review [ 10005 ] |
| Assignee | Philip Badzuh [ pbadzuh ] |
| Status | Needs 1st Level Review [ 10005 ] | First Level Review in Progress [ 10301 ] |
| Status | First Level Review in Progress [ 10301 ] | Ready for Pull Request [ 10304 ] |
| Status | Ready for Pull Request [ 10304 ] | Pull Request Submitted [ 10101 ] |
| Status | Pull Request Submitted [ 10101 ] | Reviewing Pull Request [ 10303 ] |
| Status | Reviewing Pull Request [ 10303 ] | Merged Needs Testing [ 10002 ] |
| Status | Merged Needs Testing [ 10002 ] | Post-merge Testing In Progress [ 10003 ] |
| Resolution | Done [ 10000 ] | |
| Status | Post-merge Testing In Progress [ 10003 ] | Closed [ 6 ] |
| Assignee | Philip Badzuh [ pbadzuh ] |