[prev in list] [next in list] [prev in thread] [next in thread] 

List:       xml-security-dev
Subject:    RE: resolve HTTP URI with Proxy and auth. (C version)
From:       <Dieter.Kessler () softwareag ! com>
Date:       2004-12-29 14:54:12
Message-ID: 76EEB38C72AE1D4EA2FE2753766EB5144F9933 () DAEMSG03 ! eur ! ad ! sag
[Download RAW message or body]

Hello Berin,

yes, that's what I want to do.
What you suggest sounds like a possible solution:
At the beginning I create my own Resolver object and pass all required
info (URIs plus UserId,Password, etc.) to it. Then later during signing,
the instance will check which info to resolve is required for which URI.
That should work.

Thanks,
	Dieter

-----Original Message-----
From: Berin Lautenbach [mailto:berin@wingsofhermes.org] 
Sent: Mittwoch, 29. Dezember 2004 03:17
To: security-dev@xml.apache.org
Subject: Re: resolve HTTP URI with Proxy and auth. (C version)

Ouch.  The C library is very dumb where it comes to the resolver - it
takes one and just uses it whenever it needs to resolve a URI.

Just so I'm sure of the problem scope - you are trying to use a
different resolution method for different URIs within different
references in a single signature?

You could build something "clever" into the resolver to do different
things depending on the URI passed.

The Java library has a much nicer resolver implementation, where there
is effectively a list of resolovers.  Each is asked "can you resolve
this URI" and if the answer is yes, is requested to do so.  The C++
library did something similar for Algorithm mapping, but I've never gone
back to refactor the code for the URI resolver to be more clever.

Effectively - building your own clever resolver would do the same thing
as the Java library.

Not much help I fear.

Cheers,
	Berin

Dieter.Kessler@softwareag.com wrote:

> Hi,
> 
> a while ago I've asked about a DSIGReference resolver that can do more

> than the supplied defaults.
> In particular, I needed to provide proxy information and UserId, 
> password to access a secure site.
> You replied saying that I need to provide my own resolver and hook it 
> up to xml-security via
> 	DSIGSignature::setDefaultURIResolver(MyResolver);
> Done that and it works stand-alone.
> Now I have the following problem:
> How do I pass the additional input data (proxy, userId, password) to 
> my class / DSIGReference ?
> It wouldn't be too much of a problem, if I only had one tuple of input

> parms; I set the appropriate variables in an instance of MyResolver 
> before calling setDefaultURIResolver.
> But I need to include many references that need different 
> Proxies/UserId/Password for accessing/authentication.
> 
> Any hints?
> 
> Thanks,
> 	Dieter
> 
> 
> 
> 
> 
> 

[prev in list] [next in list] [prev in thread] [next in thread]