<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<div class="moz-cite-prefix">On 5/13/14 7:49 PM, Cantor, Scott
wrote:<br>
</div>
<blockquote cite="mid:CF9827DB.CC7E%25cantor.2@osu.edu" type="cite">
<pre wrap="">Brent, it looks like the old IdP hardwired the key placement option on the
SAML Encrypter class to INLINE.</pre>
</blockquote>
<br>
Yes. I never really liked that it did that. IIRC, I don't think
Chad wanted to expose something like that as a user-visible option.<br>
<br>
<br>
<blockquote cite="mid:CF9827DB.CC7E%25cantor.2@osu.edu" type="cite">
<pre wrap=""> I could make that an option in the profile
action, but should we just make it part of the EncryptionConfig/Parameters
classes so that it's just part of the rest of the options?</pre>
</blockquote>
<br>
I was going to say yes... but I double-checked and unfortunately we
can't. That is a SAML-specific option defined on the specialized
SAML Encrypter subclass in the saml-api module. So in terms of
module dependencies it obviously wouldn't be visible to the config
and params interfaces/classes in xmlsec-api and xmlsec-impl. It
just doesn't go.<br>
<br>
Off-hand the only way I could see to make it work is if we
introduced some kind of extensible config options and associated
params, and some sort of plugin mechanism on the resolvers to handle
them. But that seems like a lot of work.<br>
<br>
I definitely agree it should be configurable somewhere, though.
Either on the action .. or maybe it's a SAML profile config option?<br>
<br>
</body>
</html>