)]}'
{"doc/source/developing.rst":[{"author":{"_account_id":11333,"name":"David J Hu","email":"david.hu@hpe.com","username":"dhu"},"change_message_id":"9cef703157c0000c65bf9115691be4a85e103e4e","unresolved":false,"context_lines":[{"line_number":167,"context_line":"identity driver (i.e. for user and group storage), allowing, for example,"},{"line_number":168,"context_line":"a different LDAP server for each domain. To ensure that Keystone can determine"},{"line_number":169,"context_line":"to which backend it should route an API call, starting with IceHouse, the"},{"line_number":170,"context_line":"identity Manager will, provided domain-specifc backends are enabled, on-the-fly"},{"line_number":171,"context_line":"a persistent mapping table between Keystone Public IDs that are presented to"},{"line_number":172,"context_line":"the controller and the domain that holds the entity, along with whatever local"},{"line_number":173,"context_line":"ID is understood by the driver.  This hides, for instance, the LDAP specifics"}],"source_content_type":"text/x-rst","patch_set":1,"id":"1ae5cdf2_7fcc7e35","line":170,"updated":"2014-06-13 21:33:51.000000000","message":"1.  ...provided \"that\" domain...\n2.  \"specific\" was misspelled","commit_id":"8c4e00974e6c08bfa192318b286729f0732d672f"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"01a0cb760dca8430dcc4dfa2425614d79aaf52ef","unresolved":false,"context_lines":[{"line_number":167,"context_line":"identity driver (i.e. for user and group storage), allowing, for example,"},{"line_number":168,"context_line":"a different LDAP server for each domain. To ensure that Keystone can determine"},{"line_number":169,"context_line":"to which backend it should route an API call, starting with IceHouse, the"},{"line_number":170,"context_line":"identity Manager will, provided domain-specifc backends are enabled, on-the-fly"},{"line_number":171,"context_line":"a persistent mapping table between Keystone Public IDs that are presented to"},{"line_number":172,"context_line":"the controller and the domain that holds the entity, along with whatever local"},{"line_number":173,"context_line":"ID is understood by the driver.  This hides, for instance, the LDAP specifics"}],"source_content_type":"text/x-rst","patch_set":1,"id":"1ae5cdf2_b19b3165","line":170,"in_reply_to":"1ae5cdf2_7fcc7e35","updated":"2014-06-17 18:10:13.000000000","message":"Done","commit_id":"8c4e00974e6c08bfa192318b286729f0732d672f"},{"author":{"_account_id":11333,"name":"David J Hu","email":"david.hu@hpe.com","username":"dhu"},"change_message_id":"9cef703157c0000c65bf9115691be4a85e103e4e","unresolved":false,"context_lines":[{"line_number":169,"context_line":"to which backend it should route an API call, starting with IceHouse, the"},{"line_number":170,"context_line":"identity Manager will, provided domain-specifc backends are enabled, on-the-fly"},{"line_number":171,"context_line":"a persistent mapping table between Keystone Public IDs that are presented to"},{"line_number":172,"context_line":"the controller and the domain that holds the entity, along with whatever local"},{"line_number":173,"context_line":"ID is understood by the driver.  This hides, for instance, the LDAP specifics"},{"line_number":174,"context_line":"of whatever ID is being used."},{"line_number":175,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"1ae5cdf2_dfb11290","line":172,"updated":"2014-06-13 21:33:51.000000000","message":"Do you mean that the persistent mapping between the controller and the domain was generated on the fly?  If yes, why not just say that.","commit_id":"8c4e00974e6c08bfa192318b286729f0732d672f"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"01a0cb760dca8430dcc4dfa2425614d79aaf52ef","unresolved":false,"context_lines":[{"line_number":169,"context_line":"to which backend it should route an API call, starting with IceHouse, the"},{"line_number":170,"context_line":"identity Manager will, provided domain-specifc backends are enabled, on-the-fly"},{"line_number":171,"context_line":"a persistent mapping table between Keystone Public IDs that are presented to"},{"line_number":172,"context_line":"the controller and the domain that holds the entity, along with whatever local"},{"line_number":173,"context_line":"ID is understood by the driver.  This hides, for instance, the LDAP specifics"},{"line_number":174,"context_line":"of whatever ID is being used."},{"line_number":175,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"1ae5cdf2_311ac1c6","line":172,"in_reply_to":"1ae5cdf2_dfb11290","updated":"2014-06-17 18:10:13.000000000","message":"the persistent mapping of ID to domain \u0026 local ID is what is built on-the-fly","commit_id":"8c4e00974e6c08bfa192318b286729f0732d672f"},{"author":{"_account_id":11045,"name":"Bob Thyne","email":"bob.thyne@hp.com","username":"bobt"},"change_message_id":"6f4f47a1ff10096786b2cc981bed3c84bbd95770","unresolved":false,"context_lines":[{"line_number":175,"context_line":""},{"line_number":176,"context_line":"To ensure backward compatibility, the default configuration of either a"},{"line_number":177,"context_line":"single SQL or LDAP backend for Identity will not use the mapping table,"},{"line_number":178,"context_line":"meaning that the public facing IDs will be the unchanged. If keeping these IDs"},{"line_number":179,"context_line":"the same for the default LDAP backend is not required, then setting the"},{"line_number":180,"context_line":"configuration variable ``backward_compatible_ids`` to ``True`` will enable"},{"line_number":181,"context_line":"the mapping for the default LDAP driver, hence hiding the LDAP specifics of the"}],"source_content_type":"text/x-rst","patch_set":1,"id":"1ae5cdf2_a410bf59","line":178,"updated":"2014-06-13 21:15:52.000000000","message":"Remove \"the\" from: \"facing IDs will be the unchanged\".","commit_id":"8c4e00974e6c08bfa192318b286729f0732d672f"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"01a0cb760dca8430dcc4dfa2425614d79aaf52ef","unresolved":false,"context_lines":[{"line_number":175,"context_line":""},{"line_number":176,"context_line":"To ensure backward compatibility, the default configuration of either a"},{"line_number":177,"context_line":"single SQL or LDAP backend for Identity will not use the mapping table,"},{"line_number":178,"context_line":"meaning that the public facing IDs will be the unchanged. If keeping these IDs"},{"line_number":179,"context_line":"the same for the default LDAP backend is not required, then setting the"},{"line_number":180,"context_line":"configuration variable ``backward_compatible_ids`` to ``True`` will enable"},{"line_number":181,"context_line":"the mapping for the default LDAP driver, hence hiding the LDAP specifics of the"}],"source_content_type":"text/x-rst","patch_set":1,"id":"1ae5cdf2_31000102","line":178,"in_reply_to":"1ae5cdf2_a410bf59","updated":"2014-06-17 18:10:13.000000000","message":"Done","commit_id":"8c4e00974e6c08bfa192318b286729f0732d672f"}]}