https://redmine.openatlas.eu/https://redmine.openatlas.eu/favicon.ico?17112826112020-07-07T08:16:31ZRedmineOpenAtlas - Feature #1299: API: Setting for CORS allowance in UI https://redmine.openatlas.eu/issues/1299?journal_id=62242020-07-07T08:16:31ZBernhard Koschiček-Krombholz
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/6224/diff?detail_id=8133">diff</a>)</li></ul> OpenAtlas - Feature #1299: API: Setting for CORS allowance in UI https://redmine.openatlas.eu/issues/1299?journal_id=62252020-07-07T09:51:59ZAlexander Watzingeralexander.watzinger@oeaw.ac.at
<ul><li><strong>Category</strong> changed from <i>UI</i> to <i>API</i></li><li><strong>Status</strong> changed from <i>New</i> to <i>Assigned</i></li><li><strong>Assignee</strong> changed from <i>Christoph Hoffmann</i> to <i>Bernhard Koschiček-Krombholz</i></li><li><strong>Target version</strong> changed from <i>Wishlist</i> to <i>5.3.0</i></li></ul><p>Beside <strong>CORS_ALLOWANCE</strong> there is also a <strong>API_SCHEMA</strong> configuration value in <strong>default.py</strong> which I could move to the API settings in backend. Since the schema is place specific I could implement it as:</p>
<ul>
<li>api_cors_allowance (default: *)</li>
<li>api_schema_place (default: <a class="external" href="https://raw.githubusercontent.com/LinkedPasts/linked-places/master/linkedplaces-context-v1.jsonld">https://raw.githubusercontent.com/LinkedPasts/linked-places/master/linkedplaces-context-v1.jsonld</a>)</li>
</ul>
<p>@ Berni: does this sound right to you? Please assign to me if answered because moving settings to backend admin is more in my area.</p> OpenAtlas - Feature #1299: API: Setting for CORS allowance in UI https://redmine.openatlas.eu/issues/1299?journal_id=62262020-07-07T10:13:27ZBernhard Koschiček-Krombholz
<ul><li><strong>Assignee</strong> changed from <i>Bernhard Koschiček-Krombholz</i> to <i>Alexander Watzinger</i></li></ul><p>Yes, sounds good to me. So it is possible to modified in the UI under Admin/Data/API?</p> OpenAtlas - Feature #1299: API: Setting for CORS allowance in UI https://redmine.openatlas.eu/issues/1299?journal_id=62272020-07-07T10:19:49ZAlexander Watzingeralexander.watzinger@oeaw.ac.at
<ul><li><strong>Subject</strong> changed from <i>Setting CORS allowance in UI </i> to <i>API: Setting for CORS allowance in UI </i></li></ul><p>Yes, I will move these 2 settings from default.py to the database (website.settings) which than can be configured in admin/data/api</p> OpenAtlas - Feature #1299: API: Setting for CORS allowance in UI https://redmine.openatlas.eu/issues/1299?journal_id=62372020-07-10T12:04:57ZAlexander Watzingeralexander.watzinger@oeaw.ac.at
<ul><li><strong>Status</strong> changed from <i>Assigned</i> to <i>Acknowledged</i></li><li><strong>Assignee</strong> deleted (<del><i>Alexander Watzinger</i></del>)</li><li><strong>Target version</strong> changed from <i>5.3.0</i> to <i>5.5.0</i></li></ul><p>Moving ticket to next version because database updates will be needed. Until now we have none for this version which makes updating instances much easier. The next version after this will have database updates anyway.<br />@ Berni: hoping this doesn't affect your development in any way.</p> OpenAtlas - Feature #1299: API: Setting for CORS allowance in UI https://redmine.openatlas.eu/issues/1299?journal_id=63822020-09-07T11:02:01ZAlexander Watzingeralexander.watzinger@oeaw.ac.at
<ul><li><strong>Status</strong> changed from <i>Acknowledged</i> to <i>Closed</i></li><li><strong>Assignee</strong> set to <i>Bernhard Koschiček-Krombholz</i></li></ul><p>Changing value in back end settings will be implemented in next version. For now it can be set in production.ini</p> OpenAtlas - Feature #1299: API: Setting for CORS allowance in UI https://redmine.openatlas.eu/issues/1299?journal_id=63892020-09-07T11:14:29ZAlexander Watzingeralexander.watzinger@oeaw.ac.at
<ul><li><strong>Target version</strong> changed from <i>5.5.0</i> to <i>5.4.0</i></li></ul>