Development Test Environment

[Brent Putman]

On 3/20/15 11:31 AM, Cantor, Scott wrote:
> Alternatively, what I tend to tell people is that for basic
> integration with the SP where the only touchpoints are the attributes
> consumed, the whole point is that you don't need the SP to produce
> the same outcome in the application. It's portable. You can spoof
> headers, manipulate the web server config, etc. to produce exactly
> the same interface to the application, and manipulate the data
> arbitrarily. That's the advantage.


For local desktop development, that's exactly what I often do.  For
Java apps, I run them locally using the Maven Jetty plugin.  I simulate
a Shib session by just using a mock servlet filter overlaid to web.xml
that exposes whatever attributes I want by setting HttpServletRequest
attributes pulled from a properties file.

That's usually good enough for what I need at the local/desktop
development stage.  Later for "real" SP testing, I handle that on an
actual (remote) test server.