Noted.
On Mon, Feb 16, 2015 at 4:49 PM, Johann Nallathamby wrote:
> Hi Chanuka,
>
> Since it is shown in the listing page lets remove it from the properties.
> Only in the backend it will be among the optional properties.
>
> On Mon, Feb 16, 2015 at 4:25 PM, Chanuka Dissanayake
> wrote:
>
>> Hi
Hi Chanuka,
Since it is shown in the listing page lets remove it from the properties.
Only in the backend it will be among the optional properties.
On Mon, Feb 16, 2015 at 4:25 PM, Chanuka Dissanayake
wrote:
> Hi,
>
> Noted. With the fix, "Disable" property is getting listed under the optional
Hi,
Noted. With the fix, "Disable" property is getting listed under the optional
properties.
Thanks.
On Mon, Feb 16, 2015 at 4:17 PM, Pushpalanka Jayawardhana
wrote:
>
>
> Pushpalanka.
> --
> Pushpalanka Jayawardhana, B.Sc.Eng.(Hons).
> Software Engineer, WSO2 Lanka (pvt) Ltd; wso2.com/
> Mob
Pushpalanka.
--
Pushpalanka Jayawardhana, B.Sc.Eng.(Hons).
Software Engineer, WSO2 Lanka (pvt) Ltd; wso2.com/
Mobile: +94779716248
Blog: pushpalankajaya.blogspot.com/ | LinkedIn:
lk.linkedin.com/in/pushpalanka/ | Twitter: @pushpalanka
On Mon, Feb 16, 2015 at 4:04 PM, Johann Nallathamby wrote:
But what about the backend? I guess it is still needed and we can have it
under optional properties right ?
On Mon, Feb 16, 2015 at 3:48 PM, Pushpalanka Jayawardhana
wrote:
> Hi All,
>
> We have taken disable/enable functionality for user stores out into
> Listing space.
> Hence we can totally r
Hi All,
We have taken disable/enable functionality for user stores out into Listing
space.
Hence we can totally remove this property from listing in UI under
properties. (Still we need the above modification)
Thanks,
Pushpalanka.
--
Pushpalanka Jayawardhana, B.Sc.Eng.(Hons).
Software Engineer, W
Hi Johann,
Following diff is the fix in user.core, and UI will be automatically
populated accordingly.
-
setMandatoryProperty(UserStoreConfigConstants.disabled,"Disabled","false",UserStoreConfigConstants.disabledDescription,
false);
+setProperty(UserStoreConfigConstants.disabled,"Disable
[adding Pushpalanka to the thread]
Why is disabled in mandadatory list in the backend. It can be optional.
Default is 'enabled'.
Can you explain. If there is not proper reason I think we can fix backend
as well as front end correctly.
Thanks.
On Mon, Feb 16, 2015 at 12:55 PM, Chanuka Dissanayak
Hi Johann,
I looked into this issue and found the followings,
This "Disabled" property is in a property list named "mandatories" in the
userstore-config.jsp file in
org.wso2.carbon.identity.user.store.configuration.ui component. It
retrieves the mandatory properties list by calling
the
UserStore
Hi Nirodha,
Thanks for pointing this out. We'll get this fixed.
Regards,
TharinduE
On Fri, Feb 13, 2015 at 5:53 PM, Nirodha Pramod wrote:
> Hi,
>
> Please see the jira [1]. In the secondary userstore UI , the user is sort
> of asked to mark the newly created userstore as disabled, by making it
Hi,
Please see the jira [1]. In the secondary userstore UI , the user is sort
of asked to mark the newly created userstore as disabled, by making it
mandatory with a checkbox. Usually in UI forms a single checkbox field is
not marked as mandatory which makes no sense. So this disabled parameter
sh
11 matches
Mail list logo
