Problem passing attribute once upgrading to version 3
Cantor, Scott
cantor.2 at osu.edu
Thu Jul 16 11:05:13 EDT 2015
On 7/16/15, 10:57 AM, "users on behalf of Todd Vernick" <users-bounces at shibboleth.net on behalf of tvernick at squarespace.com> wrote:
>Did you make any changes to saml-nameid.properties?
>
>Also what did you use for your attribute-resolver.xml?
>
>I took the default uid instance from attribute-resolver-full.xml
If you're upgrading, then upgrade. Don't change a bunch of files here. If you're starting from scratch, then I updated the documentation on the NameIDGenerationConfiguration page to outline in more detail how the process of selection works, and added an example of doing a format selection based on relying party.
If you had a working configuration with V2, you don't need to make wholesale changes. The resolver part is already functional. If you were using "unspecified" as the Format and you were triggering that with metadata, then I have explained why that broke and how to fix it (and the example in the wiki shows exactly how to fix that).
If you weren't using "unspecified", then there is no reason any of it should have been a problem.
if you're not upgrading, then the process for handling this is VERY clear. I don't know what more I can do to explain it, so please read the page again and tell me what isn't making sense and I'll supplement it.
Use your logs. If you want to know what it's doing, turn up logging and scan for categories with nameid in them or that mention the Format constant you're trying to use.
-- Scott
More information about the users
mailing list