1 Star 0 Fork 0

隐语SecretFlow / capsule-manager-sdk

加入 Gitee
与超过 1200万 开发者一起发现、参与优秀开源项目,私有仓库也完全免费 :)
免费加入
克隆/下载
贡献代码
同步代码
取消
提示: 由于 Git 不支持空文件夾,创建文件夹后会生成空的 .keep 文件
Loading...
README
Apache-2.0

CircleCI

CapsuleManager SDK

CapsuleManager sdk offers several apis to access CapsuleManager Service, which is designed to manage metadata of user data and authorization information.

Features

There are two ways to use CapsuleManager SDK:

  • If you will use sdk in source code, then you can just call functions defined in file python/sdc/capsule_manager_frame.py
  • If you will use sdk in terminal, then you can use three commands:cms, cms_util, cms_config

Quick Start

Glossary

  • CMS: Capsule Manager Service
  • Party: the user of Capsule Manager SDK
  • Resource: usually refers to data
  • Data Policy: some rules that restrict access to data, usually related to permissions

Install

pip install capsule-manager-sdk

Use sdk in source code

You can just call functions defined in file python/sdc/capsule_manager_frame.py. The function is as follows:

  • get_public_key: get CMS public key
  • register_cert: register cert of Party in CMS
  • get_data_keys: get data keys of some Resources according to the data policy from CMS
  • register_data_keys: upload data keys of some Resources to CMS
  • get_data_policys: get Data Policy of some Resources from CMS
  • register_data_policy: upload Data Policy of some Resources to CMS
  • delete_data_policy: delete Data Policy of some Resources to CMS
  • add_data_rule: for one Data Policy, add rules for it
  • delete_data_rule: for one Data Policy, delete rules for it
  • get_export_data_key: get data key for data generated from multiple datas which belong to different Partys, usually involving different Party's approval
  • delete_data_key: delete data key of a specific Resource from CMS

example:

from sdc.capsule_manager_frame import CapsuleManagerFrame

auth_frame = CapsuleManagerFrame(
    "127.0.0.1:8888",
    "1083D6017E951017EB29611024D63D4DF73445DD880D1151E776541FEBE4A776",
    None,
    True,
)
public_key_pem = auth_frame.get_public_key()
print(public_key_pem)

For more examples please see file python/tests/test_capsule_manager.py

Use sdk in terminal

There are three commands in terminal, the commands are following:

  • cms: according to the config file, call functions in file python/sdc/capsule_manager_frame.py.
  • cms_config: help generate the config file which will be used in cms command
  • cms_util: offer several convenient subcommands to use

Introduction to command cms

Command cms is the main command, it includes several subcommands which are following:

cms --help
Usage: cms [OPTIONS] COMMAND [ARGS]...

Options:
  --config-file TEXT  the config path
  --help              Show this message and exit.

Commands:
  add-data-rule         add data rule for a specific...
  delete-data-key       delete the data key of a...
  delete-data-policy    delete data policy of a...
  delete-data-rule      delete data rule for a...
  get-data-keys         get data_keys of several...
  get-data-policys      get data policy of the party...
  get-export-data-key   get the data key of export...
  get-public-key        get the pem format of public...
  register-cert         upload the cert of party...
  register-data-keys    upload data_keys of several...
  register-data-policy  upload data policy of a...

If you want to know what subcommands or parameters are supported, just use --help

# view supported subcommands
cms --help
# view supported parameters
cms --config-file=cli/cms/cli.yaml delete-data-rule --help
  • config-file: the path of config file, we will explain it in the cms_config section

  • commands: each command call one corresponding function in file python/sdc/capsule_manager_frame.py. I believe you can distinguish them from their names, for example, command get-public-key is calling function get_public_key

    cms --config-file=cli/cms/cli.yaml get-public-key
    # this will print public-key
    

Introduction to the config file

There are three parts in the config file python/cli/cli-template.yaml.

  • main section: it will be used to instantiate class CapsuleManagerFrame defined in file python/sdc/capsule_manager_frame.py

    host: "127.0.0.1"
    mr_enclave: ""
    sim: true
    root_ca_file: null
    private_key_file: null
    # List[str], cert chain file
    cert_chain_file: null
  • common section: the common config of function part

    common:
    # str
    party_id: "alice"
    # List[str], cert chain file
    cert_pems_file: null
    # str
    scheme: "RSA"
    # file contains private key
    private_key_file: null
  • function section: each section corresponds to a function call. for example, the fuction create_data_keys. As you can see, the configuration corresponds to the function parameters one-to-one.(of course, there are some function parameters in the common section)

        # function defination
        def create_data_keys(
            self,
            owner_party_id: str,
            resource_uris: List[str],
            data_keys: List[bytes],
            cert_pems: List[bytes] = None,
            private_key: Union[bytes, str, rsa.RSAPrivateKey] = None,
        ):
    
        # the function part of the config file
        register_data_keys:
            # List[str]
            resource_uris:
            # List[bytes]
            data_key_b64s:
    

After the above explanation, you should understand the design concept of this configuration file, but there are two points to note:

  1. If the content of a configuration field is too long, it will be changed to read from a file. for example, the RSA key pair:

    root_ca_file: null
    private_key_file: null
    cert_chain_file: null
  2. If the type of the content of a configuration field cannot be represented by a string, it will be changed to be represented by a string. for example, the type of data key is bytes, we will base64 encode it

    # List[bytes]
    data_key_b64s:

so, How to modify the configuration file by cms_config command?

Introduction to command cms_config

Command cms_config help modify the config file python/cli/cli-template.yaml which will be used in cms command

Command cms_config is the main command, it includes several subcommands which are following:

cms_config --help
Usage: cms_config [OPTIONS] COMMAND [ARGS]...

Options:
  --config-file TEXT  config file path
  --help              Show this message and exit.

Commands:
  add-data-rule
  common
  create-data-policy
  delete-data-policy
  delete-data-rule
  get-data-keys
  get-data-policys
  init

If you want to know what subcommands or parameters are supported, just use --help

# view supported subcommands
cms_config --help
# view supported parameters
cms_config --config-file=cli/cms/cli.yaml init --help

Since cms_config modifies the config file and the config file has three sections, so the corresponding cms_config has three types of subcommands.

  • init: modify the main section of config file
cms_config --config-file=cli/cms/cli.yaml init
  • common: modify the common section of config file
cms_config --config-file=cli/cms/cli.yaml common
  • fuctuion: modify the fuction section of config file. for example, delete-data-rule
cms_config --config-file=cli/cms/cli.yaml delete-data-rule

Please note that some parameters cannot be modified via the command cms_config, this is because we follow two principles:

  1. if the parameter type is list, it cannot be modified through the command line because click does not support nested lists.

  2. if the parameter content is too long, we do not support passing it in through the command line.

Introduction to command cms_util

Command cms_util offers several convenient subcommands to use

cms_util --help
Usage: cms_util [OPTIONS] COMMAND [ARGS]...

Options:
  --help  Show this message and exit.

Commands:
  decrypt-file               decrypt file using data key
  decrypt-file-inplace       decrypt file inplace...
  encrypt-file               encrypt file using data key
  encrypt-file-inplace       encrypt file inplace...
  generate-data-export-cert  generate the vote result...
  generate-data-key-b64      generate the base64...
  generate-party-id          generate the party id...
  generate-rsa-keypair       generate rsa key pair...

If you want to know what subcommands or parameters are supported, just use --help

# view supported subcommands
cms_util --help
# view supported parameters
cms_config decrypt-file --help

for command cms_util, just use it. for example

cms_util generate-data-key-b64
# output
emK2Imaz9f6nZNWO2hBjdA==

For most functions, you can tell what they do by their names. For a small number of functions that are difficult to understand, here is a detailed description.

  • generate-data-key-b64: generate data key and encode it with base64

  • generate-party-id: generate the identifier of party based on its certificate

  • merge-cert-chain-files: merge multiple certificate files into a certificate chain file. Note that the order of the certificates is important. The last certificate is the CA.

  • generate-data-export-cert: when exporting data, data participants are required to vote whether to agree to the data export. This function is used to generate the voting results. Since the voting results are more complicated, there is also a file python/cli/data-export-template.yaml to help generate the voting results.

The design idea of this file python/cli/data-export-template.yaml is consistent with the previous file python/cli/cli-template.yaml and is not difficult to understand.

vote_request:
  vote_request_id:
  type:
  initiator:
  vote_counter:
  voters:
    -
  executors:
    -
  approved_threshold:
  approved_action:
  rejected_action:
  # List[str], cert chain file
  cert_chain_file:
  private_key_file:
  vote_request_signature:

vote_invite:
  -
    vote_request_id:
    voter:
    action:
    # List[str], cert chain file
    cert_chain_file:
    private_key_file:
    voter_signature:

License

This project is licensed under the Apache License

Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright [yyyy] [name of copyright owner] Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

简介

调用CapsuleManager 服务的SDK 展开 收起
Python 等 3 种语言
Apache-2.0
取消

发行版

暂无发行版

贡献者

全部

近期动态

加载更多
不能加载更多了
Python
1
https://gitee.com/secretflow/capsule-manager-sdk.git
git@gitee.com:secretflow/capsule-manager-sdk.git
secretflow
capsule-manager-sdk
capsule-manager-sdk
main

搜索帮助