Issue 3047: Need TaggedComponentList typedef. (sec-rev)
Source: Syracuse University (Dr. Polar Humenn, polar(at)adiron.com)
Nature: Uncategorized Issue
Severity: 
Summary: There is a requirement to pass a sequence of IOP::TaggedComponents between
interfaces of different modules, namely SecurityReplaceable and Portable
Interceptors. 

We would like to see a typedef in module IOP of:

module IOP {
    typedef sequence<TaggedComponent> TaggedComponentList;
};

Due to different language mappings and the way they handle typdefs, a
definition in a common place is needed instead of having each module
define their own typedef for a sequence<IOP::TaggedComponent> as this
approach would provide for a difficult hand-off for the type. 

Resolution: 
Revised Text: Close Issue 2958 3044 3047
About not being able to get IOR components for
supported security mechanisms:
[Add the following end of the Vault section. Add on page 15-173
before the "The Security Context Object" header.]
create_ior_components
This operation is called to create a set of security related
TaggedComponents that indicate the security mechanisms supported by the
Vault and the given set of Credentials objects.
IOP::TaggedComponentList create_ior_components(
in SecurityLevel2::CredentialsList creds_list
);
Parameters
creds_list This argument lists the credentials that are to be
considered in creating the Tagged Components.
Return Value
This operation returns the Tagged Components. Add the following to the Consolidate IDL Appendix A.7. Security
Replaceable Service Interfaces, add:
#include <IOP.idl>
and in the definition of the Vault, add:
IOP::TaggedComponentList create_ior_components(
in SecurityLevel2::CredentialsList creds_list
);
Actions taken:
November 24, 1999: received issue
March 10, 2000: closed issue
Discussion: 

End of Annotations:=====
X-Authentication-Warning: marcy.adiron.com: polar owned process doing
-bs
Date: Wed, 24 Nov 1999 16:41:42 -0500 (EST)
From: Polar Humenn <polar@adiron.com>
To: issues@omg.org
cc: "Rutt, T E (Tom)" <terutt@lucent.com>, secrev@omg.org
Subject: Need minor addition to IOP
In-Reply-To:
<C6B3988BB062D3118BA400508B0BD0AC2FCC7D@nj7460exch009u.ho.lucent.com>
Message-ID:
<Pine.LNX.4.10.9911241618340.11683-100000@marcy.adiron.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-UIDL: P$(e9Q!4!!JA9!!\K-e9


Issue:
Document: Interop
Subject: Need TaggedComponentList typedef.
Discussion:

There is a requirement to pass a sequence of IOP::TaggedComponents
between
interfaces of different modules, namely SecurityReplaceable and
Portable
Interceptors. 

We would like to see a typedef in module IOP of:

module IOP {
    typedef sequence<TaggedComponent> TaggedComponentList;
};

Due to different language mappings and the way they handle typdefs, a
definition in a common place is needed instead of having each module
define their own typedef for a sequence<IOP::TaggedComponent> as this
approach would provide for a difficult hand-off for the type. 

The use case is:

module SecurityReplaceable {
  interface Vault {
	IOP::TaggedComponentList get_ior_components(
            in SecurityLevel2::Credentials creds_list
        );
  };
};

module PortableInterceptor {
  local interface PIBindInfo {
	void add_ior_components(
             in IOP::TaggedComponentList  components
        );
  };
};

Such that a simple hand-off in any lanaguage mapping can work.

SecurityReplaceable::Vault_var       vault     = ...;
PortableInterceptor::PIBindInfo_var pibindinfo = ...;
Security::CredentialsList_var       creds_list = ...;

IOP::TaggedComponentList_var components = 
                              vault->get_ior_components(creds_list.in());
pibindinfo->add_ior_components( components.in() );

     (please forgive any mistakes in my C++ mapping)

We would like to take advantage of this type in the upcoming Security
RTF.

We would need a resolution date prior to Dec 3rd as that is when the
Security RTF will delay the start of its next vote on related issues.

Thanks,
-Polar