Request for SAML attributes mapping configuration between Okta to Shibboleth IDP

[Cantor, Scott]

> We tried to use “xsi:type=StoredSAML” to store the SAML
> attribute and utilized the same for mapping against the
> attribute IDs at Shibboleth end. But we could find in one of
> the articles that StoredSAML type is deprecated from V4.3.1
> onwards.

There has never been such a "type" in Shibboleth, so whatever you're talking about, it isn't our software, no matter what version.

Properly configuring attribute decoding rules with the registry, and adding appropriate inbound filtering rules, will store off idPAttributes into the Subject produced by the proxy login flow.

The Subject DataConnector can extract them in the resolver when processing other (front-channel) requests without much extra work.

All documented.

-- Scott