offapi/com/sun/star/xml/crypto/XXMLEncryptionTemplate.idl

   1 /* -*- Mode: C++; tab-width: 4; indent-tabs-mode: nil; c-basic-offset: 4 -*- */
   2 /*
   3  * This file is part of the LibreOffice project.
   4  *
   5  * This Source Code Form is subject to the terms of the Mozilla Public
   6  * License, v. 2.0. If a copy of the MPL was not distributed with this
   7  * file, You can obtain one at http://mozilla.org/MPL/2.0/.
   8  *
   9  * This file incorporates work covered by the following license notice:
  10  *
  11  *   Licensed to the Apache Software Foundation (ASF) under one or more
  12  *   contributor license agreements. See the NOTICE file distributed
  13  *   with this work for additional information regarding copyright
  14  *   ownership. The ASF licenses this file to you under the Apache
  15  *   License, Version 2.0 (the "License"); you may not use this file
  16  *   except in compliance with the License. You may obtain a copy of
  17  *   the License at http://www.apache.org/licenses/LICENSE-2.0 .
  18  */
  19
  20 module com { module sun { module star { module xml { module crypto {
  21
  22 /**
  23  * Interface of XML encryption template
  24  *
  25  * <p>This interface represents an encryption template, which is the same as the
  26  * desired XML encryption element[ EncryptedType ] but some of the nodes may be
  27  * empty. The empty entities include CipherValue, which is a subset of
  28  * EncryptedData or EncryptedKey. Empty entities are not allowed in an encryption
  29  * template when performing decryption.</p>
  30  *
  31  * <p>In some cases, the encryptor or decryptor can determine and locate the
  32  * EncryptedKey from the encryption template by dereference the RetrievalMethod
  33  * inside EncryptedData.</p>
  34  *
  35  * <p>In some cases, the EncryptedKey need to be clearly pointed out by the
  36  * encryption template.</p>
  37  *
  38  * <p>With the help of encryption context, the encryptor or decryptor specifies
  39  * the key from the KeyInfo in the encryption template.</p>
  40  *
  41  *
  42  * <p>It isn't a good method to set the EncryptedKey here. In general, there is
  43  * a RetrievalMethod in EncryptedData by which we can get the EncryptedKey.
  44  *
  45  * And sometimes, in the low level, it is hard to determine what the key is
  46  * except that the high level application tell the mechanism and parameters.
  47  *
  48  * So I think it will be more simple that the application set the encrypted key
  49  * information. In this case, the application only need to know the XML schema
  50  * or DTD and the encryption device. If so, the high level application takes the
  51  * action of build the EncryptedKey template and references it in the element of
  52  * EncryptedData. And in this case, the calling to set up EncryptedKey template
  53  * and target is not necessary, because the encryptor or decryptor can determine
  54  * and locate the EncryptedKey from the encryption template of EncryptedData by
  55  * dereference the RetrievalMethod.
  56  *
  57  * In some situation, the high level applications do not want to know anything
  58  * about crypto devices( May be he must, because the lower level do not know
  59  * what the key is ). If it gives the key value, it can get EncryptedKey by
  60  * setting the key template and key value target.</p>
  61  */
  62 interface XXMLEncryptionTemplate : XXMLSecurityTemplate
  63 {
  64     /**
  65      * Get the target XML element, i.e. the element to be encrypted
  66      */
  67     com::sun::star::xml::wrapper::XXMLElementWrapper getTarget(
  68     ) ;
  69 } ;
  70
  71 } ; } ; } ; } ; } ;
  72
  73 /* vim:set shiftwidth=4 softtabstop=4 expandtab: */