Hi Shiro team,
I am currently integrating Shiro into our application.

We have our own component-based configuration system which needs to
operate as follows:
- start user database component
- start Shiro PasswordService component
- start Shiro SeurityManager component
- start embedded Jetty web server

I can quite happily perform the first three steps, but when I start
the web server it currently reads a Shiro INI file in
IniWebEnvironment and sets up a second SecurityManager. Instead, I
want the existing static SecurityManager to be used. (I want to
continue using the INI file to setup the filters from the [main] and
[urls] section).

Have I missed something, or do I just have to hack around with the
WebEnvironment to write a subclass that re-uses the static
SecurityManager?

In the embedded Jetty scenario, I think most users would want to
re-use a static SecurityManager that has been separately created.

Also, as a detail, PasswordMatcher could really do with an additional
constructor that takes the PasswordService.

thanks
Stephen

Reply via email to