<div dir="ltr"><div>I saw that the RequiredActionProviderRepresentation & RequiredActionProviderModel already </div><div>provide a Map<String,String> config to store additional config settings.</div><div><br></div><div>Would it be enough to expose this RequiredActions configuration in the same way it is done </div><div>in the AuthenticationFlows via "actions -> config" in the admin console?</div><div><br></div><div>Cheers,</div><div>Thomas</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">2016-03-09 6:54 GMT+01:00 Stian Thorgersen <span dir="ltr"><<a href="mailto:sthorger@redhat.com" target="_blank">sthorger@redhat.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">You can create a JIRA for the ability to have configurable required actions. That won't be until 2.x though.<div><br></div><div>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.</div></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="h5">On 8 March 2016 at 18:41, Josh Cain <span dir="ltr"><<a href="mailto:josh.cain@redhat.com" target="_blank">josh.cain@redhat.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr"><div><div>Hi all,<br><br></div>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?<br><br></div>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?<span><font color="#888888"><br><div><div><div><br clear="all"><div><div><div dir="ltr"><span><div><div>Josh Cain | Software Applications Engineer<br></div><i>Identity and Access Management</i><br></div><b>Red Hat</b><br><a href="tel:%2B1%20843-737-1735" value="+18437371735" target="_blank">+1 843-737-1735</a><br></span></div></div></div>
</div></div></div></font></span></div>
<br></div></div>_______________________________________________<br>
keycloak-dev mailing list<br>
<a href="mailto:keycloak-dev@lists.jboss.org" target="_blank">keycloak-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/keycloak-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/keycloak-dev</a><br></blockquote></div><br></div>
<br>_______________________________________________<br>
keycloak-dev mailing list<br>
<a href="mailto:keycloak-dev@lists.jboss.org">keycloak-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/keycloak-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/keycloak-dev</a><br></blockquote></div><br></div>