Can EncryptionMethod be specified per SP and not in SP metadata?
Mohamed Lrhazi
lrhazi at cua.edu
Wed Jan 15 03:39:11 UTC 2025
So I tried this, but it seems to still be using aes128-gcm:
<MetadataProvider
id="HTTPMetadatalawlibOverdrive"
xsi:type="FilesystemMetadataProvider"
metadataFile="%{idp.home}/metadata/lawOverdrive.xml">
<MetadataFilter xsi:type="Algorithm">
<md:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#aes128-cbc"
/>
</MetadataFilter>
</MetadataProvider>
What am I doing wrong?
On Tue, Jan 14, 2025 at 8:51 PM Mohamed Lrhazi <lrhazi at cua.edu> wrote:
> metadata filters looks simple enough! Thank you!
>
> On Tue, Jan 14, 2025 at 7:33 PM Cantor, Scott via users <
> users at shibboleth.net> wrote:
>
>> >Is this possible?
>>
>> Yes, with lots of very ugly XML [1], but there's no reason to and it's
>> ill-advised, it should be done with metadata or metadata filters.
>>
>> -- Scott
>>
>> [1]
>> https://shibboleth.atlassian.net/wiki/spaces/IDP5/pages/3199508797/SecurityConfiguration
>>
>> --
>> For Consortium Member technical support, see
>> https://shibboleth.atlassian.net/wiki/x/ZYEpPw
>> To unsubscribe from this list send an email to
>> users-unsubscribe at shibboleth.net
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20250114/eeece07f/attachment.htm>
More information about the users
mailing list