Handling New User Memberships

Brandon McKean mckeanbs at jmu.edu
Wed May 10 16:49:14 EDT 2017

I believe I've found the culprit. I had left this in from the prior example:

>  p:attributeContextLookupStrategy-ref="shibboleth.ChildLookupOrCreate.AttributeContext"
Looks like it wasn't needed, and removing it makes it all work as expected.

Brandon McKean
IT / Systems
Linux Administrator

On 05/10/2017 04:37 PM, Cantor, Scott wrote:
> On 5/10/17, 4:21 PM, "users on behalf of Brandon McKean" <users-bounces at shibboleth.net on behalf of mckeanbs at jmu.edu> wrote:
>> Though now I'm getting a different error. Here's an example of what I
>> get with memberOf:
>>> 2017-05-10 16:14:47,948 - ERROR
>>> [net.shibboleth.idp.attribute.context.AttributeContext:100] - No
>>> Attributes have been set in this flow.
> For that to happen in the context-check interceptor, the resolver had to have not run, or produced no attributes (and the latter isn't exactly an error per se so the message being logged that way is questionable, but it's pretty unusual).
> It would make more sense that the resolver failed and the system was configured to mask it as non-fatal and continue along, and there would be plenty of logging about it.
> -- Scott

More information about the users mailing list