Issue 1766:   Credentials not in SecurityReplaceable. (sec-rev)
Source:  (, )
Nature:  Clarification
Severity:  Critical
Summary: Summary: It would appear since the SecurityContext must hold onto the
 Credentials object, that the Credentials object must appear
 in SecurityReplaceable as well, since there is no factory
 for generation of credentials in an independant way.
 
 Perhaps a "Server Context should have a list of
 security attributes instead of a list of credentials.
 That way an orb using a replacable module can create a local
 credentials object and put the security attributes in it.
 
 

Resolution: 
Revised Text: 
Actions taken:
August 2, 1998: received issue
November 13, 1998: closed issue
Discussion: 

End of Annotations:=====
Return-Path: <www>
Date: Sun, 2 Aug 1998 18:19:58 -0400
From: www
To: juergen@omg.org, web-incoming@omg.org
Subject: WWW Form output

Name: Polar Humenn
Company: Adiron, LLC
Email: polar@adiron.com
Notification: Yes
Specification: Services (Security)
Section: 15.7.2.3
Formal #: who-knows
Version: CORBAsec v1.2 Draft
Revision_Date: 5 jan 1998
Page: 15-91
Nature: Clarification
Severity: Critical
full_desc: Credentials not in SecurityReplaceable.

It would appear since the SecurityContext must hold onto the
Credentials object, that the Credentials object must appear
in SecurityReplaceable as well, since there is no factory
for generation of credentials in an independant way.

Perhaps a "Server Context should have a list of
security attributes instead of a list of credentials.
That way an orb using a replacable module can create a local
credentials object and put the security attributes in it.
submit: Submit Issue Report