getInboundMessageTransport always returns a null value

[Paul Hethmon]

On May 27, 2015, at 3:32 PM, Cantor, Scott <cantor.2 at osu.edu> wrote:
> 
>> We are using the Multi Context Broker to provide two-factor authentication.  The MCB plugin logs the the peer IP address so I know that this is available at the point just prior to doing attribute resolution. I wonder if there is an issue with the requestContext as it is passed from the MCB nto the attribute resolver code?
> 
> There is, he has to mock up that object essentially and I doubt it has all those properties populated. So that's the issue.

I’m getting ready to do a couple of changes/fixes to the MCB, if you could put an issue into the Github issue tracker for MCB, I can certainly add the peer ip address the request context.

cheers,

Paul


-----
Paul Hethmon
Chief Software Architect
paul.hethmon at clareitysecurity.com