)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":27900,"name":"Artem Goncharov","email":"artem.goncharov@gmail.com","username":"gtema"},"change_message_id":"9b999ec7a15cc680aac06879885833fb55277925","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"a6b61b65_ff185c05","updated":"2025-07-18 14:12:57.000000000","message":"I does not make sense for the REST api","commit_id":"2294884f0300aaaf6011a2342629528d355bb466"},{"author":{"_account_id":2218,"name":"Adam Young","email":"adam@younglogic.com","username":"ayoung"},"change_message_id":"7cfd5e461d4ccca6a9d4aa097019459be9749807","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"c18b99cb_ebf8e278","in_reply_to":"a6b61b65_ff185c05","updated":"2025-07-18 16:11:28.000000000","message":"Of course  it does.  Nothing about REST says that it is ONLY for machine consumption. \n\nUsing the Keystone API from the Browser would make most Keystone use cases implemented at the same time for interactive user/ browser and for automated CLI implementation.  It would simplify the learning curve for administrators. And it would clarify where the Keystone API falls down on discover ability.\n\nKeystone IS exposed to the end user,  necessarily so Federated Identity.  The fact that it shows a JSON RPC message is unhelpful.","commit_id":"2294884f0300aaaf6011a2342629528d355bb466"}]}