Please confirm that this is a bug. If yes, can we have this fixed? We
really wanted this feature in our project ASAP. Please let me know what can
be done about this.
On Thu, Jul 21, 2016 at 7:18 AM, Stian Thorgersen <sthorger(a)redhat.com>
wrote:
Looks like a bug then - Bill any comments?
On 20 July 2016 at 09:12, Rashmi Singh <singhrasster(a)gmail.com> wrote:
> For now, I want the default value to show up in the admin console only
> when looking at the config of the authenticator. The issue is that the
> default value I am setting for the properties in authenticatorFactory are
> not showing up on the admin console when you look at the authenticator ->
> config. I see the properties displayed there but they dont show the default
> values I set in the factory class. For booleans, it always show false and
> for string types, always blank and not what I set. I am not looking for the
> default values in AuthenticationFlowContext.getAuthenticatorConfig. I
> am looking for it in the admin console only. I expected this to work but it
> doesn't. Is it a bug?
>
> On Wed, Jul 20, 2016 at 1:04 AM, Stian Thorgersen <sthorger(a)redhat.com>
> wrote:
>
>> It looks like the default value is only used in the admin console to
>> show a default value for the option when configuring the authenticator. The
>> default values are not added to
>> AuthenticationFlowContext.getAuthenticatorConfig unless the authenticator
>> is first configured through the admin console. It would be better if it was
>> though so default values would always be available. Feel free to create an
>> enhancement JIRA issue for it.
>>
>> On 19 July 2016 at 16:23, Rashmi Singh <singhrasster(a)gmail.com> wrote:
>>
>>> Infact, not only Boolean, it does not seem to work for even properties
>>> that are STRING_TYPE. I was using 1.9.4 version earlier but now I tried
>>> with the latest 2.0.0 version too and it does not work on either. What is
>>> the issue?
>>>
>>> On Tue, Jul 19, 2016 at 7:00 AM, Rashmi Singh <singhrasster(a)gmail.com>
>>> wrote:
>>>
>>>> Bruno, I had tried "true" also but that did not work either.
Forgot to
>>>> mention in my original post. I am not sure why true or "true"
doesn't work
>>>> if that's expected. Is there a bug? Does anyone have a clue on this?
>>>>
>>>> On Tue, Jul 19, 2016 at 4:13 AM, Bruno Oliveira
<bruno(a)abstractj.org>
>>>> wrote:
>>>>
>>>>> Hi Rashmi, try "true" instead of true. Take a look at
this:
>>>>>
https://github.com/keycloak/keycloak/blob/f6a718f10a3a3a07a6222bea7d8b58e...
>>>>>
>>>>> In theory, should work.
>>>>>
>>>>> On 2016-07-18, Rashmi Singh wrote:
>>>>> > In my AuthenticatorFactory class, I have the following
>>>>> configuration added:
>>>>> >
>>>>> > ProviderConfigProperty property;
>>>>> > property= new ProviderConfigProperty();
>>>>> > property.setName("propname");
>>>>> > property.setLabel("Property Name");
>>>>> > property.setDefaultValue(true);
>>>>> > property.setType(ProviderConfigProperty.BOOLEAN_TYPE);
>>>>> > configProperties.add(identityFirstproperty);
>>>>> >
>>>>> > I wanted to keep a default value as true and at first it seemed
>>>>> like the
>>>>> > following line would do it:
>>>>> >
>>>>> > property.setDefaultValue(true);
>>>>> >
>>>>> > But that does not seem to work. The default is still false. How
can
>>>>> I set
>>>>> > the default to true?
>>>>>
>>>>> > _______________________________________________
>>>>> > keycloak-dev mailing list
>>>>> > keycloak-dev(a)lists.jboss.org
>>>>> >
https://lists.jboss.org/mailman/listinfo/keycloak-dev
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>> abstractj
>>>>> PGP: 0x84DC9914
>>>>>
>>>>
>>>>
>>>
>>> _______________________________________________
>>> keycloak-dev mailing list
>>> keycloak-dev(a)lists.jboss.org
>>>
https://lists.jboss.org/mailman/listinfo/keycloak-dev
>>>
>>
>>
>