Scoping an attribute

[Dave Vernon]

AWESOME!!!  Thanks so much, that worked!  (The example from Scott's code)

I think the problem with the documentation is more with me, than with the wording.  Somewhere during my reading I read a very detailed non-official guide that said that very clearly..  I think that I... projected... my desires onto it.  Looking at the official documentation with fresh eyes, I don't see it suggested.

I can't thank you all enough, I don't think I would have got there on my own!

(Next stop is integrating with ADFS, but I wanted to make sure I had a native Shib install working)


Dave Vernon
Technology Infrastructure Specialist
dvernon at loyalistc.on.ca
loyalistcollege.com




-----Original Message-----
From: users-bounces at shibboleth.net [mailto:users-bounces at shibboleth.net] On Behalf Of Cantor, Scott
Sent: Monday, October 06, 2014 2:28 PM
To: Shib Users
Subject: Re: Scoping an attribute

On 10/6/14, 2:20 PM, "Dave Vernon" <dvernon at loyalistcollege.com> wrote:

>I thought that the ScopedAttributeDecoder was supposed to drop the 
>domain portion.. at least that was my understanding from the documentation.

If you identify the wording that led you to that conclusion, I'll fix it.

>Any ideas what I¹m missing to allow ONLY the username portion to be 
>delivered?

My OSU example file has commented out content for constructing a custom header we use locally for an unqualified ID (WHOIS-ID). [1]

-- Scott

[1]
https://webauth.service.ohio-state.edu/~shibboleth/config/2.5/shibboleth2.x
ml

--
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net