OpenSAML user discussion

["Singh, Manish" <>]

Brent,

I spent a little time looking at the source but did not find any issue.
I am expecting to put my application (uses OpenSaml 2.0 lib) under heavy
load test in May (hopefully and prod in July) which would give us real
results (positive hopefully).

I just wanted to make sure that I cover all my bases if you already know
of any concurrency concerns in these classes.

I will surely update everyone after this load test (We are a SP so far)

Thanks,
Manish

-----Original Message-----
From: Brent Putman 
[mailto:]
 
Sent: Friday, April 04, 2008 6:40 PM
To: 

Subject: Re: [OpenSAML] Thread Safe classes

MessageDecoders and SecurityPolicyRules are required to be thread-safe,
and I double-checked those 2 and pretty sure they're fine.  The
signature profile validator doesn't have any state, it should also be
fine.  I didn't write the parser pool, there are a few areas there that
appear a little sketchy with respect to concurrency, but nothing that
would affect typical usage and fundamental operation.

All are used heavily in our Shibboleth 2.0 IdP in a multi-threaded
manner, we haven't seen any issues yet.

Did you see anything in particular in the code or behavior that would
lead you to believe otherwise?  If so, feel free to report or file a
bug.

--Brent


Singh, Manish wrote:
> It seems safe to assume based on browsing through these classes that 
> they are thread safe but would be better if author could confirm this.
>
> org.opensaml.security.SAMLSignatureProfileValidator
> org.opensaml.saml2.binding.decoding.HTTPPostDecoder
> org.opensaml.xml.parse.BasicParserPool
> org.opensaml.common.binding.security.MessageReplayRule
>
> Thanks,
> Manish
>