RE: [security-services] New (minor) Issue: AuthNMethod,not Confi rmationMethod in AuthNQu ery

[Irving Reid <Irving.Reid@baltimore.com>]

> From: Hal Lockhart [mailto:hal.lockhart@entegrity.com]
> In the AuthenticationQuery, it is possible to provide
> an optional ConfirmationMethod. 
> I believe the intent here was to specify an AuthenticationMethod.
> (Prateek says this is an old bug that never got fixed.)

> Spcifically, 
> line 1282, 1298 and 2324 change "ConfirmationMethod"
> to "AuthenticationMethod" 
> line 1285 change "confirmation" to "authentication" 
> Hal 


I'm not so sure about this. I recall some discussion of people wanting to
say "Give me an authn assertion, if you have one that contains
ConfirmationMethod 'foo'." That way, the requester could go on and perform
the confirmation to make sure they're talking to the right subject.

However, this isn't something I'm interested in supporting, so don't have a
problem with your change.

 - irving -


-----------------------------------------------------------------------------------------------------------------
The information contained in this message is confidential and is intended 
for the addressee(s) only.  If you have received this message in error or 
there are any problems please notify the originator immediately.  The 
unauthorized use, disclosure, copying or alteration of this message is 
strictly forbidden. Baltimore Technologies plc will not be liable for direct, 
special, indirect or consequential damages arising from alteration of the 
contents of this message by a third party or as a result of any virus being 
passed on.

 
This footnote confirms that this email message has been swept by 
Baltimore MIMEsweeper for Content Security threats, including
computer viruses.