Uploaded image for project: 'Couchbase .NET client library'
  1. Couchbase .NET client library
  2. NCBC-1650

Create example for field level encryption

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.6.0-beta, 2.6.0
    • Component/s: docs
    • Labels:

      Description

      In support of users of the devguide-examples and possible high-level conceptual documentation and other samples being created, add on master branch of devguide-examples two examples. They may be in the same code file.

      First, an example that shows how to encrypt a field in a document, store it and read it back.

      Second, given a specific document and the necessary keys and other information, show how one would read encrypted fields. It's expected that for this one, the keys would be in files in standard formats in the repository. The same set of files should work for all SDK implementations.

      Use the .NET example as a pattern.

      • Include JSON files of the data
      • The standard file format is PKCS#8 and PKCS#12 for windows/dotnet

        Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

          Show
          jmorris Jeff Morris added a comment - Example can be found here: https://github.com/couchbaselabs/devguide-examples/blob/master/dotnet/FieldEncryption.cs
          Hide
          ingenthr Matt Ingenthron added a comment -

          It's expected that for this one, the keys would be in files in standard formats in the repository. The same set of files should work for all SDK implementations.

          Looks like you may have overlooked this requirement. It's important so that way multiple implementations can start with the same inputs. e.g., I expect the same keys to actually be in the repo as example.

          Show
          ingenthr Matt Ingenthron added a comment - It's expected that for this one, the keys would be in files in standard formats in the repository. The same set of files should work for all SDK implementations. Looks like you may have overlooked this requirement. It's important so that way multiple implementations can start with the same inputs. e.g., I expect the same keys to actually be in the repo as example.
          Hide
          jmorris Jeff Morris added a comment -

          The keys I used were the same as the keys in the RFC along with all of additional intermediate data in the tables for verification across all SDKs: https://docs.google.com/document/d/1qxn-Rv4Uh9wW_9ZGssQGGQElOgxi3FS6-nzy8zJUgdk/edit#heading=h.tzc2tnrnpc9c

          Show
          jmorris Jeff Morris added a comment - The keys I used were the same as the keys in the RFC along with all of additional intermediate data in the tables for verification across all SDKs: https://docs.google.com/document/d/1qxn-Rv4Uh9wW_9ZGssQGGQElOgxi3FS6-nzy8zJUgdk/edit#heading=h.tzc2tnrnpc9c
          Hide
          ingenthr Matt Ingenthron added a comment -

          Note the reference to using files. I think we chatted about that too.

          Show
          ingenthr Matt Ingenthron added a comment - Note the reference to using files. I think we chatted about that too.
          Show
          jmorris Jeff Morris added a comment - https://github.com/couchbaselabs/devguide-examples/pull/23

            People

            • Assignee:
              jmorris Jeff Morris
              Reporter:
              ingenthr Matt Ingenthron
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Gerrit Reviews

                There are no open Gerrit changes

                  PagerDuty

                  Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.