IdP v4.1.0 as a proxy between OIDC client and SAML Federation
Felipe Cardoso
felipepassoscardoso at gmail.com
Mon May 10 18:14:13 UTC 2021
Thanks Scott.
After your tip and a more detailed reading of the documentation, I was able
to define the attributes to be incorporated into the token.
I was confusing "idp.oidc.embeddedAttributes" with
"idp.oidc.encodedAttributes".
But now the scenario is working as expected.
Regards,
Em seg., 10 de mai. de 2021 às 09:21, Cantor, Scott <cantor.2 at osu.edu>
escreveu:
> On 5/7/21, 6:44 PM, "users on behalf of Felipe Cardoso" <
> users-bounces at shibboleth.net on behalf of felipepassoscardoso at gmail.com>
> wrote:
>
> > Is it possible to implement this scenario?
>
> If the attributes are solely available on the front channel then the only
> way to make them available on the back channel is by encoding them into the
> token(s). That's a documented option on the profile bean should be covered
> in the docs.
>
> -- Scott
>
>
> --
> For Consortium Member technical support, see
> https://wiki.shibboleth.net/confluence/x/coFAAg
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net
>
--
Felipe Cardoso
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20210510/6a7d03b7/attachment.htm>
More information about the users
mailing list