unable to configure DataSealer decrypt
Giuseppe Giacomini
giuseppe.giacomini at unive.it
Mon Mar 7 16:13:16 UTC 2022
Scott, thanks for your comments
now I understand where I went wrong.
I saved the encrypted seed value in ldap user entry and modified the
attribute resolver as shown below:
<AttributeDefinition xsi:type="Decrypted"
dataSealerRef="totp.DataSealer" id="tokenSeeds">
<InputDataConnector ref="ldapUnive" attributeNames="TotpSeeds"/>
</AttributeDefinition>
Now it seems to work.
I hope I haven't made any other mistake
Thank you
On Mon, 7 Mar 2022 at 15:29, Cantor, Scott <cantor.2 at osu.edu> wrote:
> Why are you attaching an AttributeEncoder here (or any of the rest of that
> stuff)? You don't seriously intend to pass this out to an SP, not to
> mention I think that's the name for sn (last name).
>
> I imagine the data you're sourcing isn't encrypted properly in the first
> place, only the log would say for sure.
>
> -- Scott
>
>
> --
> 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
>
--
Giacomini Giuseppe
Università Ca' Foscari Venezia
ASIT- Settore Sistemi
giuseppe.giacomini at unive.it
tel. 041 234 7118
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20220307/d6351d8f/attachment.htm>
More information about the users
mailing list