Hi Johann, Both the "attributes" and "filter" can be used together in IS 5.3.0. Please see the last example at [1].
[1] https://medium.com/@pulasthi7/scim-list-users-with-given-attributes-in-wso2-identity-server-5-3-0-8360522d3ea9 On Wed, Aug 2, 2017 at 2:10 PM, Johann Nallathamby <joh...@wso2.com> wrote: > Hi Chamila, > > On Wed, Aug 2, 2017 at 2:06 PM, Chamila Wijayarathna < > cdwijayarat...@gmail.com> wrote: > >> Hi Johann, >> >> Sorry for the confusion, I didn't knew about SCIM attributes >> implementation previously. Is this only available for SCIM 2.0 or is this >> available in SCIM 1.x implementation as well? >> > > This is there from IS 5.3.0 onwards. > > >> >> If it is supported in SCIM list, it should be there in filter also. >> Because AFAIK, filter is parameter we pass to list operation. Filter is not >> a different operation from list. If I explain it more, what we refer as >> filter is a overloaded function of list. >> > > Exactly. > > >> >> eg : User List(); >> User List (String filter); >> >> So filter operation should return a same type of objects, but may be a >> less number. If they behave differently, IMO it is wrong. >> >> So +1 for implementing attributes here as well. >> > > Thanks for your feedback. > > Regards, > Johann. > > >> >> Regards! >> Chamila >> >> On Wed, Aug 2, 2017 at 6:23 PM, Johann Nallathamby <joh...@wso2.com> >> wrote: >> >>> >>> >>> On Tue, Jul 11, 2017 at 6:52 PM, Chamila Wijayarathna < >>> cdwijayarat...@gmail.com> wrote: >>> >>>> Hi Johann, >>>> >>>> In IS 5.0 >>>> filter=username eq name >>>> gave the result that you are expecting here, but we changed it to >>>> return only meta data since retrieving all attributes is costly. Spec also >>>> mentions that query should minimally return meta data, returning additional >>>> data or all data is also compliant with the spec IIRC. >>>> >>> >>> Correct. >>> >>> >>>> >>>> So in my opinion, what you are suggesting here is moving back to the >>>> old functionality we had and I believe if we are to do that, we will have >>>> to do that at the cost of performance. I suppose this may not as costly as >>>> 2 network calls if filter returns only 1 result. But it is not guaranteed >>>> in filter or attribute thing you are suggesting that it will return only 1 >>>> result, so still performance can be a issue. >>>> >>> >>> No. I am not saying to move back to old implementation. I am saying to >>> implement "attributes" feature to SCIM filtering also. Currently we have it >>> only for SCIM listing. So if we implement that, by default filtering will >>> return only metadata. And if needed extra attributes, we can specifically >>> request like in SCIM listing. >>> >>> Regards, >>> Johann. >>> >>> >>>> >>>> Cheers >>>> Chamila >>>> >>>> On Tue, Jul 11, 2017 at 11:08 PM, Johann Nallathamby <joh...@wso2.com> >>>> wrote: >>>> >>>>> Hi IAM Team, >>>>> >>>>> Can we support "attributes" feature for SCIM filter query? Right now >>>>> SCIM filter query returns only metadata. It doesn't return additional >>>>> attributes. Therefore we have to do at least two network calls if we need >>>>> to get user's attributes using username. Can we do this in one call >>>>> network >>>>> call? >>>>> >>>>> "attributes" feature for /Users GET allows to retrieve any number of >>>>> additional attributes we want apart from the metadata. This is very >>>>> convenient to avoid too many network calls. If the same is available for >>>>> SCIM filter query it will be great I think. >>>>> >>>>> I checked the spec but couldn't find anything. Spec seems to be silent >>>>> on it. Any expert opinion on this subject? >>>>> >>>>> Regards, >>>>> Johann. >>>>> >>>>> -- >>>>> >>>>> *Johann Dilantha Nallathamby* >>>>> Senior Lead Solutions Engineer >>>>> WSO2, Inc. >>>>> lean.enterprise.middleware >>>>> >>>>> Mobile - *+94777776950* >>>>> Blog - *http://nallaa.wordpress.com <http://nallaa.wordpress.com>* >>>>> >>>>> _______________________________________________ >>>>> Dev mailing list >>>>> Dev@wso2.org >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> Chamila Dilshan Wijayarathna, >>>> PhD Research Student >>>> The University of New South Wales (UNSW Canberra) >>>> Australian Centre for Cyber Security >>>> Australian Defence Force Academy >>>> PO Box 7916, Canberra BA ACT 2610 >>>> Australia >>>> Mobile:(+61)416895795 <+61%20416%20895%20795> >>>> >>>> >>> >>> >>> -- >>> Thanks & Regards, >>> >>> *Johann Dilantha Nallathamby* >>> Senior Lead Solutions Engineer >>> WSO2, Inc. >>> lean.enterprise.middleware >>> >>> Mobile - *+94777776950* >>> Blog - *http://nallaa.wordpress.com <http://nallaa.wordpress.com>* >>> >> >> >> >> -- >> Chamila Dilshan Wijayarathna, >> PhD Research Student >> The University of New South Wales (UNSW Canberra) >> Australian Centre for Cyber Security >> Australian Defence Force Academy >> PO Box 7916, Canberra BA ACT 2610 >> Australia >> Mobile:(+61)416895795 <+61%20416%20895%20795> >> >> > > > -- > Thanks & Regards, > > *Johann Dilantha Nallathamby* > Senior Lead Solutions Engineer > WSO2, Inc. > lean.enterprise.middleware > > Mobile - *+94777776950* > Blog - *http://nallaa.wordpress.com <http://nallaa.wordpress.com>* > > _______________________________________________ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Pulasthi Mahawithana* Senior Software Engineer WSO2 Inc., http://wso2.com/ Mobile: +94-71-5179022 Blog: https://medium.com/@pulasthi7/ <https://wso2.com/signature>
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
