Shibboleth Developers

[Brent Putman <>]

Another way would be to use Spring.  Just define the value as a Spring
bean (even a plain String can be a bean) in say internal.xml, and then
it's accessible from anywhere you can get at the Spring app context.
The "easy" way would be to just assume a fixed bean id and then just
hardcode that bean id in your LoginHandler's bean definition parser and
servlet init code.  Servlet can get access to the Spring app context
using standard Spring conventions.



On 12/7/10 4:06 PM, Christopher Bongaarts wrote:
> I'm creating a new LoginHandler extension to implement some features of
> our existing web SSO system.  I basically took the existing RemoteUser
> LoginHandler as a basis, and made a couple small tweaks.  So I have a
> RemoteUserLoginHandler that issues a redirect to a RemoteUserAuthServlet.
> 
> I have a configuration item that I want to set once (as an element in
> the <LoginHandler> declaration in handler.xml), but need to retrieve the
> value from both the LoginHandler and the AuthServlet.  What would be the
> best way to approach this?
> 
> In the worst case I'll just end up hardcoding the value, but it would be
> really nice to be able to change this variable without recompiling.