overridding admin interface beans/flows
Bobby Lawrence
robertl at jlab.org
Tue Dec 13 21:17:48 UTC 2022
Background- I'm upgrading from 3.4.7 to 4.2.1.
We use the in-memory account lockout feature but found that the admin REST interface to manage lockouts doesn't provide enough in its GET output. We wanted to have the ability to list all of the current lockouts so that we didn't need to know the exact lockout key. So I created my own "DoLockoutManagerOperation" bean and injected into the IdP via an extension. I believe that order to make it work, I had to effectively copy the entire admin/lockout flow XML files into my jar file because simply creating another DoLockoutManagerOperation bean in my postconfig.xml or classpath:/net/shibboleth/idp/flows/admin/lockout-beans.xml or even in global.xml wasn't enough.
This stuff now doesn't work in 4.2.1. I'm getting an error that effectively prevents the IdP from even deploying....an error that looks like this:
java.lang.IllegalStateException: Illegal attempt to register pre-existing flow ID 'admin/lockout'via resource: URL [jar:file:/opt/apache-tomcat-9.0.68/webapps/idp/WEB-INF/lib/mis-security-shibboleth.jar!/META-INF/net/shibboleth/idp/flows/admin/lockout/lockout-flow.xml
Is there not any way to override the admin flows in 4.x? How can I override the "DoLockoutManagerOperation" bean and inject in my own version that provides more JSON?
Thanks in advance Scott :)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20221213/36df8f01/attachment.htm>
More information about the users
mailing list