)]}'
{"specs/juno/endpoint-cert.rst":[{"author":{"_account_id":11045,"name":"Bob Thyne","email":"bob.thyne@hp.com","username":"bobt"},"change_message_id":"685cfea3976d99309dd209b463e3e21c341eedd3","unresolved":false,"context_lines":[{"line_number":5,"context_line":" http://creativecommons.org/licenses/by/3.0/legalcode"},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":8,"context_line":"Endpoint Authentication  X509 Certificates"},{"line_number":9,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"`bp example \u003chttps://blueprints.launchpad.net/keystone/+spec/endpoint-cert\u003e`_"}],"source_content_type":"text/x-rst","patch_set":1,"id":"1ae5cdf2_db422167","line":8,"updated":"2014-06-13 05:34:28.000000000","message":"Double spacing before X509 ... Are we missing \"via\"?","commit_id":"0396e6408e78203be13189608cfc807654cb8d58"},{"author":{"_account_id":11045,"name":"Bob Thyne","email":"bob.thyne@hp.com","username":"bobt"},"change_message_id":"685cfea3976d99309dd209b463e3e21c341eedd3","unresolved":false,"context_lines":[{"line_number":11,"context_line":"`bp example \u003chttps://blueprints.launchpad.net/keystone/+spec/endpoint-cert\u003e`_"},{"line_number":12,"context_line":""},{"line_number":13,"context_line":""},{"line_number":14,"context_line":"Allow endpoints to authenticate via X509 certificates specific to each endpoint."},{"line_number":15,"context_line":""},{"line_number":16,"context_line":""},{"line_number":17,"context_line":"Problem Description"}],"source_content_type":"text/x-rst","patch_set":1,"id":"1ae5cdf2_de7a0f76","line":14,"updated":"2014-06-13 05:34:28.000000000","message":"Do we need \"specific to each endpoint\" or is this a given based on the nature of the beast we call X.509? What about simply:\n\nAllow endpoints to authenticate via X.509 certificate-based authentication.","commit_id":"0396e6408e78203be13189608cfc807654cb8d58"},{"author":{"_account_id":11045,"name":"Bob Thyne","email":"bob.thyne@hp.com","username":"bobt"},"change_message_id":"685cfea3976d99309dd209b463e3e21c341eedd3","unresolved":false,"context_lines":[{"line_number":19,"context_line":""},{"line_number":20,"context_line":"Endpoints need to be able to authenticate to Keystone to perform actions that"},{"line_number":21,"context_line":"are specific to endpoints:  fetch the token revocation information, and fetch"},{"line_number":22,"context_line":"their policy files.  Reusing a service user across multipl endpoint has security"},{"line_number":23,"context_line":"implications.  Instea, each end point should have its own identity."},{"line_number":24,"context_line":""},{"line_number":25,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"1ae5cdf2_3eda1378","line":22,"updated":"2014-06-13 05:34:28.000000000","message":"A couple of typos nested in this paragraph:\n- extra space before \"fetch the token ...\"\n- multipl\n- Instea\n- end point\n\nDo we need the phrase \"that are specific to endpoints\"? What about simply: \n\n\"\nEndpoints need to be able to authenticate to Keystone in order to retrieve token revocation information and policy files.\n\"\n\nCan we expand on policy files?","commit_id":"0396e6408e78203be13189608cfc807654cb8d58"},{"author":{"_account_id":220,"name":"Haneef Ali","email":"haneef.ali@hp.com","username":"haneef"},"change_message_id":"4f733a0da6b23c68a841f6244ccc3ad3c539aa12","unresolved":false,"context_lines":[{"line_number":19,"context_line":""},{"line_number":20,"context_line":"Endpoints need to be able to authenticate to Keystone to perform actions that"},{"line_number":21,"context_line":"are specific to endpoints:  fetch the token revocation information, and fetch"},{"line_number":22,"context_line":"their policy files.  Reusing a service user across multipl endpoint has security"},{"line_number":23,"context_line":"implications.  Instea, each end point should have its own identity."},{"line_number":24,"context_line":""},{"line_number":25,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"1ae5cdf2_4a50465e","line":22,"updated":"2014-06-26 04:46:12.000000000","message":"Why do you think service user is re used?  if  a deployment can make a poor decision of reusing service user, then what prevents them from reusing the same certificate across multiple endpoint.  I don\u0027t think this a valid point","commit_id":"0396e6408e78203be13189608cfc807654cb8d58"},{"author":{"_account_id":220,"name":"Haneef Ali","email":"haneef.ali@hp.com","username":"haneef"},"change_message_id":"4f733a0da6b23c68a841f6244ccc3ad3c539aa12","unresolved":false,"context_lines":[{"line_number":30,"context_line":""},{"line_number":31,"context_line":"We treat endpoints like  users; instead of one set of credentials that is"},{"line_number":32,"context_line":"copied to each Nova etc we give each a distinct Identity.  They should be "},{"line_number":33,"context_line":"using an X509 to authenticate to Keystone.  "},{"line_number":34,"context_line":""},{"line_number":35,"context_line":" The X509 can be self signed by the endpoint for all we really care, although it means that we will have a bunch of CAs.  Better to have them issued by Keystone"},{"line_number":36,"context_line":"by default.   It has to be x509 for PKI because you can\u0027t do SSH style plain"}],"source_content_type":"text/x-rst","patch_set":1,"id":"1ae5cdf2_8a46cea5","line":33,"updated":"2014-06-26 04:46:12.000000000","message":"Whitespace","commit_id":"0396e6408e78203be13189608cfc807654cb8d58"},{"author":{"_account_id":11045,"name":"Bob Thyne","email":"bob.thyne@hp.com","username":"bobt"},"change_message_id":"685cfea3976d99309dd209b463e3e21c341eedd3","unresolved":false,"context_lines":[{"line_number":33,"context_line":"using an X509 to authenticate to Keystone.  "},{"line_number":34,"context_line":""},{"line_number":35,"context_line":" The X509 can be self signed by the endpoint for all we really care, although it means that we will have a bunch of CAs.  Better to have them issued by Keystone"},{"line_number":36,"context_line":"by default.   It has to be x509 for PKI because you can\u0027t do SSH style plain"},{"line_number":37,"context_line":"key based authentication on the web and Kerberos is too high a barrier to entry."},{"line_number":38,"context_line":""},{"line_number":39,"context_line":"However, this approach should be extensible to Kerberos in a separate blueprint."}],"source_content_type":"text/x-rst","patch_set":1,"id":"1ae5cdf2_9b333913","line":36,"updated":"2014-06-13 05:34:28.000000000","message":"x509 \u003d\u003e X509\n\nBTW are we ignoring the period/dot? X509 \u003d\u003e X.509","commit_id":"0396e6408e78203be13189608cfc807654cb8d58"},{"author":{"_account_id":11045,"name":"Bob Thyne","email":"bob.thyne@hp.com","username":"bobt"},"change_message_id":"685cfea3976d99309dd209b463e3e21c341eedd3","unresolved":false,"context_lines":[{"line_number":34,"context_line":""},{"line_number":35,"context_line":" The X509 can be self signed by the endpoint for all we really care, although it means that we will have a bunch of CAs.  Better to have them issued by Keystone"},{"line_number":36,"context_line":"by default.   It has to be x509 for PKI because you can\u0027t do SSH style plain"},{"line_number":37,"context_line":"key based authentication on the web and Kerberos is too high a barrier to entry."},{"line_number":38,"context_line":""},{"line_number":39,"context_line":"However, this approach should be extensible to Kerberos in a separate blueprint."},{"line_number":40,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"1ae5cdf2_fe0a6b1e","line":37,"updated":"2014-06-13 05:34:28.000000000","message":"Get rid of \"style plain\" and re-phrase to SSH key-based authentication.\n\nIs it worth mentioning briefly why SSH key-based authentication is not workable on the web? I\u0027m assuming the headache of managing SSH keys plays a part.","commit_id":"0396e6408e78203be13189608cfc807654cb8d58"},{"author":{"_account_id":11045,"name":"Bob Thyne","email":"bob.thyne@hp.com","username":"bobt"},"change_message_id":"685cfea3976d99309dd209b463e3e21c341eedd3","unresolved":false,"context_lines":[{"line_number":36,"context_line":"by default.   It has to be x509 for PKI because you can\u0027t do SSH style plain"},{"line_number":37,"context_line":"key based authentication on the web and Kerberos is too high a barrier to entry."},{"line_number":38,"context_line":""},{"line_number":39,"context_line":"However, this approach should be extensible to Kerberos in a separate blueprint."},{"line_number":40,"context_line":""},{"line_number":41,"context_line":"Even with eventlet we can do X509 based client auth."},{"line_number":42,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"1ae5cdf2_3e10534d","line":39,"updated":"2014-06-13 05:34:28.000000000","message":"I would only keep this line if we have a reference to an existing bug/blueprint. Or do we have a \"Future Work\" section in the spec template?","commit_id":"0396e6408e78203be13189608cfc807654cb8d58"},{"author":{"_account_id":136,"name":"Tim Bell","email":"tim.bell@cern.ch","username":"tim-bell"},"change_message_id":"9441374300a5365750952df0df5a3e425095fd85","unresolved":false,"context_lines":[{"line_number":36,"context_line":"by default.   It has to be x509 for PKI because you can\u0027t do SSH style plain"},{"line_number":37,"context_line":"key based authentication on the web and Kerberos is too high a barrier to entry."},{"line_number":38,"context_line":""},{"line_number":39,"context_line":"However, this approach should be extensible to Kerberos in a separate blueprint."},{"line_number":40,"context_line":""},{"line_number":41,"context_line":"Even with eventlet we can do X509 based client auth."},{"line_number":42,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"1ae5cdf2_c918ad86","line":39,"updated":"2014-06-30 06:42:16.000000000","message":"Is https://blueprints.launchpad.net/keystone/+spec/kerberos-authentication the one to refer to ? Most of this seems to be implemented already and thus I would hope that X.509 support would be looking to re-use the approach that Kerberos has taken rather than a new one. Sites that have to configure both X.509 and Kerberos (such as CERN) would really prefer to not have two different architectures.","commit_id":"0396e6408e78203be13189608cfc807654cb8d58"},{"author":{"_account_id":11045,"name":"Bob Thyne","email":"bob.thyne@hp.com","username":"bobt"},"change_message_id":"685cfea3976d99309dd209b463e3e21c341eedd3","unresolved":false,"context_lines":[{"line_number":38,"context_line":""},{"line_number":39,"context_line":"However, this approach should be extensible to Kerberos in a separate blueprint."},{"line_number":40,"context_line":""},{"line_number":41,"context_line":"Even with eventlet we can do X509 based client auth."},{"line_number":42,"context_line":""},{"line_number":43,"context_line":"Endpoints credentials will be kept in an new column in the endpoint table."},{"line_number":44,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"1ae5cdf2_1e4d573e","line":41,"updated":"2014-06-13 05:34:28.000000000","message":"X.509 certificate-based authentication","commit_id":"0396e6408e78203be13189608cfc807654cb8d58"},{"author":{"_account_id":220,"name":"Haneef Ali","email":"haneef.ali@hp.com","username":"haneef"},"change_message_id":"4f733a0da6b23c68a841f6244ccc3ad3c539aa12","unresolved":false,"context_lines":[{"line_number":45,"context_line":"Upon or after an endpoint is registered, an admin will upload a Client"},{"line_number":46,"context_line":"Certificate for the endpoint."},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"This sounds like it _needs_ barbican (or something similar for the services "},{"line_number":49,"context_line":" cert management/ca) for a professional deployment."},{"line_number":50,"context_line":""},{"line_number":51,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"1ae5cdf2_8addeedf","line":48,"updated":"2014-06-26 04:46:12.000000000","message":"Whitespace","commit_id":"0396e6408e78203be13189608cfc807654cb8d58"},{"author":{"_account_id":220,"name":"Haneef Ali","email":"haneef.ali@hp.com","username":"haneef"},"change_message_id":"4f733a0da6b23c68a841f6244ccc3ad3c539aa12","unresolved":false,"context_lines":[{"line_number":49,"context_line":" cert management/ca) for a professional deployment."},{"line_number":50,"context_line":""},{"line_number":51,"context_line":""},{"line_number":52,"context_line":" endpoints would then act as users (using a token to get the policy, etc)? and"},{"line_number":53,"context_line":" use those credentials to get policy ,and also to get revocation lists etc."},{"line_number":54,"context_line":""},{"line_number":55,"context_line":"Tokens issued this way shoud not have a user_id in it.  They should have the endpoint_id in them instead."}],"source_content_type":"text/x-rst","patch_set":1,"id":"1ae5cdf2_6af7c25a","line":52,"updated":"2014-06-26 04:46:12.000000000","message":"I really don\u0027t understand the flow. Admin upload\u0027s client cert. After that what happens? How is it used?   Can you add one use case on how it is used? Who is using this client cert and how is it used?","commit_id":"0396e6408e78203be13189608cfc807654cb8d58"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"dc1d8bccfe7afda0df84f57e30a94c23feadbc6d","unresolved":false,"context_lines":[{"line_number":70,"context_line":"Alternatives"},{"line_number":71,"context_line":"------------"},{"line_number":72,"context_line":""},{"line_number":73,"context_line":"Create one service user per endpoint.  This will break in AD cases where Identity is read only.  it will work if we put some users in SQL, but it means that endpoint are going to use Paswords, which is not a secure authentication mechanism."},{"line_number":74,"context_line":""},{"line_number":75,"context_line":"X509 and user authentication could be built the same way."},{"line_number":76,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"dab895d6_e712a057","line":73,"updated":"2014-06-30 06:35:37.000000000","message":"if you use henrys multiple backends support? then it wouldn\u0027t break AD?\n\nbut yes, it would still mean using passwords","commit_id":"0396e6408e78203be13189608cfc807654cb8d58"},{"author":{"_account_id":11045,"name":"Bob Thyne","email":"bob.thyne@hp.com","username":"bobt"},"change_message_id":"685cfea3976d99309dd209b463e3e21c341eedd3","unresolved":false,"context_lines":[{"line_number":86,"context_line":"REST API Impact"},{"line_number":87,"context_line":"---------------"},{"line_number":88,"context_line":""},{"line_number":89,"context_line":"POST /ednpointcert"},{"line_number":90,"context_line":""},{"line_number":91,"context_line":"body of the post should be the X509 for the endpoint."},{"line_number":92,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"1ae5cdf2_7b510d2f","line":89,"updated":"2014-06-13 05:34:28.000000000","message":"Should it be POST /endpointcert?","commit_id":"0396e6408e78203be13189608cfc807654cb8d58"},{"author":{"_account_id":11045,"name":"Bob Thyne","email":"bob.thyne@hp.com","username":"bobt"},"change_message_id":"685cfea3976d99309dd209b463e3e21c341eedd3","unresolved":false,"context_lines":[{"line_number":94,"context_line":"Security Impact"},{"line_number":95,"context_line":"---------------"},{"line_number":96,"context_line":""},{"line_number":97,"context_line":"Ovewrall should tighent up security:  PKI is less vulnerable than passwords.  It will require more X509 infrastrucutre in the Keystone server:  both SSL by"},{"line_number":98,"context_line":"default and X50-9 client certificate checking are handled wlell by apache"},{"line_number":99,"context_line":"modules. But they can be done via Eventlet if needed."},{"line_number":100,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"1ae5cdf2_5e019fad","line":97,"updated":"2014-06-13 05:34:28.000000000","message":"typos: \n- Ovewrall\n- tighent\n- infrastrucutre\n- wlell\n- apache\n\nDo we have existing endpoint authentication capabilities i.e. Does password-based authentication already exist for endpoints?","commit_id":"0396e6408e78203be13189608cfc807654cb8d58"},{"author":{"_account_id":11045,"name":"Bob Thyne","email":"bob.thyne@hp.com","username":"bobt"},"change_message_id":"685cfea3976d99309dd209b463e3e21c341eedd3","unresolved":false,"context_lines":[{"line_number":95,"context_line":"---------------"},{"line_number":96,"context_line":""},{"line_number":97,"context_line":"Ovewrall should tighent up security:  PKI is less vulnerable than passwords.  It will require more X509 infrastrucutre in the Keystone server:  both SSL by"},{"line_number":98,"context_line":"default and X50-9 client certificate checking are handled wlell by apache"},{"line_number":99,"context_line":"modules. But they can be done via Eventlet if needed."},{"line_number":100,"context_line":""},{"line_number":101,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"1ae5cdf2_1e747766","line":98,"updated":"2014-06-13 05:34:28.000000000","message":"typo: X50-9","commit_id":"0396e6408e78203be13189608cfc807654cb8d58"},{"author":{"_account_id":11045,"name":"Bob Thyne","email":"bob.thyne@hp.com","username":"bobt"},"change_message_id":"685cfea3976d99309dd209b463e3e21c341eedd3","unresolved":false,"context_lines":[{"line_number":107,"context_line":"Other End User Impact"},{"line_number":108,"context_line":"---------------------"},{"line_number":109,"context_line":""},{"line_number":110,"context_line":"There will need to be corresponding changes to keystone client to take advantage of the,m"},{"line_number":111,"context_line":""},{"line_number":112,"context_line":"Performance Impact"},{"line_number":113,"context_line":"------------------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"1ae5cdf2_fe598bfd","line":110,"updated":"2014-06-13 05:34:28.000000000","message":"the,m?","commit_id":"0396e6408e78203be13189608cfc807654cb8d58"},{"author":{"_account_id":11045,"name":"Bob Thyne","email":"bob.thyne@hp.com","username":"bobt"},"change_message_id":"685cfea3976d99309dd209b463e3e21c341eedd3","unresolved":false,"context_lines":[{"line_number":112,"context_line":"Performance Impact"},{"line_number":113,"context_line":"------------------"},{"line_number":114,"context_line":""},{"line_number":115,"context_line":"SSL in eventlet is slow."},{"line_number":116,"context_line":""},{"line_number":117,"context_line":""},{"line_number":118,"context_line":"Other Deployer Impact"}],"source_content_type":"text/x-rst","patch_set":1,"id":"1ae5cdf2_be31c3a3","line":115,"updated":"2014-06-13 05:34:28.000000000","message":"Is evidence required here? I\u0027m assuming not although always nice for a link or add a link to the reference section.","commit_id":"0396e6408e78203be13189608cfc807654cb8d58"},{"author":{"_account_id":11045,"name":"Bob Thyne","email":"bob.thyne@hp.com","username":"bobt"},"change_message_id":"685cfea3976d99309dd209b463e3e21c341eedd3","unresolved":false,"context_lines":[{"line_number":118,"context_line":"Other Deployer Impact"},{"line_number":119,"context_line":"---------------------"},{"line_number":120,"context_line":""},{"line_number":121,"context_line":"More x509 generation, which will benfit from a real CA solution."},{"line_number":122,"context_line":""},{"line_number":123,"context_line":""},{"line_number":124,"context_line":"Developer Impact"}],"source_content_type":"text/x-rst","patch_set":1,"id":"1ae5cdf2_7e13bb00","line":121,"updated":"2014-06-13 05:34:28.000000000","message":"typo: \n- x509\n- benfit\n\nRe-phrase: \"real CA solution\"","commit_id":"0396e6408e78203be13189608cfc807654cb8d58"},{"author":{"_account_id":11045,"name":"Bob Thyne","email":"bob.thyne@hp.com","username":"bobt"},"change_message_id":"685cfea3976d99309dd209b463e3e21c341eedd3","unresolved":false,"context_lines":[{"line_number":122,"context_line":""},{"line_number":123,"context_line":""},{"line_number":124,"context_line":"Developer Impact"},{"line_number":125,"context_line":"----------------"},{"line_number":126,"context_line":""},{"line_number":127,"context_line":""},{"line_number":128,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"1ae5cdf2_bed8e353","line":125,"updated":"2014-06-13 05:34:28.000000000","message":"Developer Impact - testing?","commit_id":"0396e6408e78203be13189608cfc807654cb8d58"},{"author":{"_account_id":11045,"name":"Bob Thyne","email":"bob.thyne@hp.com","username":"bobt"},"change_message_id":"685cfea3976d99309dd209b463e3e21c341eedd3","unresolved":false,"context_lines":[{"line_number":158,"context_line":""},{"line_number":159,"context_line":"References"},{"line_number":160,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":161,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"1ae5cdf2_bebf03cf","line":161,"updated":"2014-06-13 05:34:28.000000000","message":"No references?","commit_id":"0396e6408e78203be13189608cfc807654cb8d58"}]}
