)]}'
{"security-guide/section_dashboard-session-back-end.xml":[{"author":{"_account_id":6547,"name":"Andreas Jaeger","email":"jaegerandi@gmail.com","username":"jaegerandi"},"change_message_id":"15751083ae235042da9161fa69099d3906d1de34","unresolved":false,"context_lines":[{"line_number":6,"context_line":"  xml:id\u003d\"dashboard-session-back-end\"\u003e"},{"line_number":7,"context_line":"  \u003c?dbhtml stop-chunking?\u003e"},{"line_number":8,"context_line":"      \u003ctitle\u003eSession back end\u003c/title\u003e"},{"line_number":9,"context_line":"      \u003cpara\u003eThe default session back end for Horizon"},{"line_number":10,"context_line":"\t(\u003cliteral\u003edjango.contrib.sessions.backends.signed_cookies\u003c/literal\u003e)"},{"line_number":11,"context_line":"\tsaves user data in signed, but unencrypted cookies stored in the"},{"line_number":12,"context_line":"        browser. Due to the fact that each dashboard instance is"}],"source_content_type":"application/xml","patch_set":1,"id":"fa32b979_34210ffc","line":9,"updated":"2015-06-16 09:59:28.000000000","message":"lower case horizon - see our conventions at https://wiki.openstack.org/wiki/Documentation/Conventions#Service_and_project_names","commit_id":"58b4e0b1a606b83e3705d5f9192181908744649b"},{"author":{"_account_id":167,"name":"Christian Berendt","email":"berendt@osism.tech","username":"berendt"},"change_message_id":"1207086ba865b9bb0cd9436d2845ad96702e8339","unresolved":false,"context_lines":[{"line_number":12,"context_line":"        browser. Due to the fact that each dashboard instance is"},{"line_number":13,"context_line":"\tstateless, the previously mentioned methodology provides the"},{"line_number":14,"context_line":"\tability to implement the most simple session back-end scaling."},{"line_number":15,"context_line":"\tIt should be noted that with this type of implementation "},{"line_number":16,"context_line":"\tsensitive access tokens will be stored in the rowser and will be"},{"line_number":17,"context_line":"\ttransmitted with each request made. The back end ensures the "},{"line_number":18,"context_line":"\tintegrity of session data, even though the ransmitted data "}],"source_content_type":"application/xml","patch_set":1,"id":"fa32b979_949fbb4f","line":15,"updated":"2015-06-16 09:55:57.000000000","message":"Remove trailing whitespaces.","commit_id":"58b4e0b1a606b83e3705d5f9192181908744649b"},{"author":{"_account_id":167,"name":"Christian Berendt","email":"berendt@osism.tech","username":"berendt"},"change_message_id":"1207086ba865b9bb0cd9436d2845ad96702e8339","unresolved":false,"context_lines":[{"line_number":16,"context_line":"\tsensitive access tokens will be stored in the rowser and will be"},{"line_number":17,"context_line":"\ttransmitted with each request made. The back end ensures the "},{"line_number":18,"context_line":"\tintegrity of session data, even though the ransmitted data "},{"line_number":19,"context_line":"\tis only encrypted by HTTPS.\u003c/para\u003e"},{"line_number":20,"context_line":"      \u003cpara\u003eIf your architecture allows it, we recommend using"},{"line_number":21,"context_line":"        \u003cliteral\u003edjango.contrib.sessions.backends.cache\u003c/literal\u003e as"},{"line_number":22,"context_line":"        your session back end with memcache as the cache. Memcache must"}],"source_content_type":"application/xml","patch_set":1,"id":"fa32b979_54a9337a","line":19,"updated":"2015-06-16 09:55:57.000000000","message":"Do not use tabs.","commit_id":"58b4e0b1a606b83e3705d5f9192181908744649b"},{"author":{"_account_id":8450,"name":"Christian Wolter","email":"wolter@b1-systems.de","username":"cwolter"},"change_message_id":"7f497bec28fb559e51fa6a437daec0f84785bf2c","unresolved":false,"context_lines":[{"line_number":22,"context_line":"        your session back end with memcache as the cache. Memcache must"},{"line_number":23,"context_line":"        not be exposed publicly, and should communicate over a secured"},{"line_number":24,"context_line":"        private channel. If you choose to use the signed cookies"},{"line_number":25,"context_line":"        back end, refer to the Django documentation understand the"},{"line_number":26,"context_line":"        security trade-offs.\u003c/para\u003e"},{"line_number":27,"context_line":"      \u003cpara\u003eFor further details, see the \u003clink"},{"line_number":28,"context_line":"        xlink:href\u003d\"https://docs.djangoproject.com/\""}],"source_content_type":"application/xml","patch_set":3,"id":"fa32b979_3d232c07","line":25,"updated":"2015-06-16 12:49:50.000000000","message":"This should be \"documentation to understand the\"","commit_id":"0dbeff72b031dcccfeeb9bc90b95ce7da3bdc661"},{"author":{"_account_id":12325,"name":"Nathaniel Dillon","email":"nathaniel.dillon@alumni.depaul.edu","username":"sicarie"},"change_message_id":"dc95be009a3626104854cde90dd70132f4ddc503","unresolved":false,"context_lines":[{"line_number":11,"context_line":"        saves user data in signed, but unencrypted cookies stored in the"},{"line_number":12,"context_line":"        browser. Due to the fact that each dashboard instance is"},{"line_number":13,"context_line":"        stateless, the previously mentioned methodology provides the"},{"line_number":14,"context_line":"        ability to implement the most simple session back-end scaling.\u003c/para\u003e"},{"line_number":15,"context_line":"      \u003cpara\u003eIt should be noted that with this type of implementation"},{"line_number":16,"context_line":"        sensitive access tokens will be stored in the browser and will be"},{"line_number":17,"context_line":"        transmitted with each request made. The back end ensures the"}],"source_content_type":"application/xml","patch_set":4,"id":"fa32b979_6c0d808f","line":14,"updated":"2015-06-16 14:31:14.000000000","message":"Unfortunately I\u0027m awful at identifying parts of speech - is this the proper part of speech for putting a hyphen/emdash on back-end (as opposed to lines 9 or 17)?","commit_id":"24a36b0d614c316b928a2f10b13d5f231dbe85c7"}]}