You can create a JIRA for the ability to have configurable required actions. That won't be until 2.x though. Using an authenticator instead has the downside that it can't be assigned as a default action, nor can it be assigned to a selected user. I can't see any other immediate downsides. You could for instance have an attribute on a user that determines if the action should be executed or not though. On 8 March 2016 at 18:41, Josh Cain <josh.cain(a)redhat.com&gt; wrote: > Hi all, > > I'm working on a required action that needs a bit of configuration. I'd > ideally like to manage this in the same way that I manage my current > federation provider/authenticator SPI implementations, but I don't see a > way to do so. Is there a way to configure these via Keycloak? > > If not, I'm considering just writing said action as an authenticator and > including it in the authentication flow. Would there be any downsides to > this approach? > > Josh Cain | Software Applications Engineer > *Identity and Access Management* > *Red Hat* > +1 843-737-1735 > > _______________________________________________ > keycloak-dev mailing list > keycloak-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/keycloak-dev > _______________________________________________ keycloak-dev mailing list keycloak-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/keycloak-dev