{"id":29,"date":"2011-11-08T21:38:02","date_gmt":"2011-11-08T21:38:02","guid":{"rendered":"http:\/\/www.w3.org\/community\/webcryptoapi\/?p=29"},"modified":"2012-03-28T21:47:41","modified_gmt":"2012-03-28T21:47:41","slug":"web-certificates-service-api","status":"publish","type":"post","link":"https:\/\/www.w3.org\/community\/webcryptoapi\/2011\/11\/08\/web-certificates-service-api\/","title":{"rendered":"Web Certificates Service API?"},"content":{"rendered":"<p>Now <a href=\"http:\/\/lists.w3.org\/Archives\/Public\/public-identity\/2011Nov\/thread.html\" target=\"_blank\" rel=\"nofollow\">many discussions<\/a> are goning on scopes of Web Cryptography working group<\/a> charter. I think many of use-cases in cryptography API focused in certificate authority service with personal certificates.<\/p>\n<p>But, this is hard to consider another working group because of PKI based systems too. (Most of countries has own national CA system based on plug-in issuing personal certificate such as China, Japan, Spain and Brazil etc.) So I suggested adding parallel works for *Web Certificates (Service)<br \/>\nAPI* supporting these. We can add these as a scope including TLS\/SSL based login\/out with personal certificate and its management api(backup, restore)<br \/>\nand follow up HSM based certificate.<\/p>\n<p>Especially in Firefox, the validation of security device based on FIPS is already possible. (Other browser?) I guess Web Certificate Service API is needed to treat this kind of interfaces in future. Anyway we have better focus on primitive APIs for light-weight usecases. Because all browsers have own key stroage. \ud83d\ude42<\/p>\n<p>Please give a comment for my suggestions:<br \/>\n[1] http:\/\/lists.w3.org\/Archives\/Public\/public-identity\/2011Nov\/0012.html<br \/>\n[2] http:\/\/lists.w3.org\/Archives\/Public\/public-identity\/2011Nov\/0025.html<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Now many discussions are goning on scopes of Web Cryptography working group charter. I think many of use-cases in cryptography API focused in certificate authority service with personal certificates. But, this is hard to consider another working group because of &hellip; <a href=\"https:\/\/www.w3.org\/community\/webcryptoapi\/2011\/11\/08\/web-certificates-service-api\/\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":318,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_s2mail":"yes","footnotes":""},"categories":[1],"tags":[18,17],"class_list":["post-29","post","type-post","status-publish","format-standard","hentry","category-uncategorized","tag-key-management","tag-tls-login"],"_links":{"self":[{"href":"https:\/\/www.w3.org\/community\/webcryptoapi\/wp-json\/wp\/v2\/posts\/29","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.w3.org\/community\/webcryptoapi\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.w3.org\/community\/webcryptoapi\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.w3.org\/community\/webcryptoapi\/wp-json\/wp\/v2\/users\/318"}],"replies":[{"embeddable":true,"href":"https:\/\/www.w3.org\/community\/webcryptoapi\/wp-json\/wp\/v2\/comments?post=29"}],"version-history":[{"count":1,"href":"https:\/\/www.w3.org\/community\/webcryptoapi\/wp-json\/wp\/v2\/posts\/29\/revisions"}],"predecessor-version":[{"id":30,"href":"https:\/\/www.w3.org\/community\/webcryptoapi\/wp-json\/wp\/v2\/posts\/29\/revisions\/30"}],"wp:attachment":[{"href":"https:\/\/www.w3.org\/community\/webcryptoapi\/wp-json\/wp\/v2\/media?parent=29"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.w3.org\/community\/webcryptoapi\/wp-json\/wp\/v2\/categories?post=29"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.w3.org\/community\/webcryptoapi\/wp-json\/wp\/v2\/tags?post=29"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}