"ServletRequest was null" warning in IdP 3.3.0

[Robert A Basch]

We are not stuck on the deprecated syntax, so much as never bothered
to update it on this IdP.  We will convert it to the new syntax, and
will follow up only if the problem persists.

Thanks,
Bob


> On Feb 28, 2017, at 8:13 PM, Cantor, Scott <cantor.2 at osu.edu> wrote:
> 
> On 2/28/17, 7:55 PM, "users on behalf of Robert A Basch" <users-bounces at shibboleth.net on behalf of rbasch at mit.edu> wrote:
> 
>> The IdP seems to be functioning properly, though; at least SPs are happily
>> consuming the resulting assertions.  Can anyone provide info as to what the
>> warning means, and advise as to what might be causing it?
> 
> Any chance you're stuck on the deprecated relying-party syntax perhaps?
> 
> I don't see any way for that to happen otherwise (and I'm just guessing that it might be a regression with that case since it's been enough years now and so few people have actually used that compatibility support).
> 
> The warning means the profile configuration beans don't have access to that object and that doesn't generally matter apart from advanced configurations that are plugging in scripts to derive the settings, which was a feature introduced in 3.3.
> 
> The necessary bean references are in relying-party-system.xml so I'm just surmising that the only way this could really happen is with a legacy configuration.
> 
> -- Scott
> 
> 
> -- 
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net