On Tue, Jun 7, 2016 at 6:35 PM, Hasintha Indrajee <hasin...@wso2.com> wrote:
> Hi Damith, > > For the time being we can follow this approach. But this seems like a > standard problem we may face in other products as well. Any standard way of > handling this ? Any ideas for handling this issue in future ? > > Hmm, AFAIK above was not became an issue for other analytics products/usecases .. @Srinath and all, do you guys have any suggestions ? what should be the best approach ?.. Thanks, Mohan > On Tue, Jun 7, 2016 at 12:32 PM, Damith Wickramasinghe <dami...@wso2.com> > wrote: > >> Hi Johann and all, >> >> Our decided approach was to send a empty string for all the cases from IS >> side and from DAS after retrieving data, provide a default string with some >> style to show that its a special empty case. But in lucene we cannot have >> empty attributes since they cannot be indexed and search will not work for >> them. Our next option is to provide a standard naming for a default value >> and also provide some configuration in IS to change it if needed. WDYT ? >> >> Regards, >> Damith. >> >> On Mon, Jun 6, 2016 at 7:19 PM, Damith Wickramasinghe <dami...@wso2.com> >> wrote: >> >>> Hi, >>> >>> When it comes to authentication scenarios in some cases we cannot >>> specify roles etc to publishing events eg:- non existing user tried to >>> login with username and password. Then for the said events roles attribute >>> will be empty/null . >>> >>> Also as discussed with Pulasthi there can be other attributes as well >>> which can be empty or null. For all those scenarios we need to show a >>> authentication failure count for all the dimensions of User, Role, >>> IdentityProvider etc.For that we need a constant String which can be used >>> to show the respective fail counts. Having a constant value like >>> "NOT-AVAILABLE" can be sent from IS side or populated from DAS side but any >>> user can create an username of any sort . eg:NOT-AVAILABLE .So there can be >>> issues in calculating authentication failure counts. >>> >>> Any insights on handling such scenarios ? >>> >>> Regards, >>> Damith. >>> >>> -- >>> Software Engineer >>> WSO2 Inc.; http://wso2.com >>> <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> >>> lean.enterprise.middleware >>> >>> mobile: *+94728671315 <%2B94728671315>* >>> >>> >> >> >> -- >> Software Engineer >> WSO2 Inc.; http://wso2.com >> <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> >> lean.enterprise.middleware >> >> mobile: *+94728671315 <%2B94728671315>* >> >> > > > -- > Hasintha Indrajee > Software Engineer > WSO2, Inc. > Mobile:+94 771892453 > > -- *V. Mohanadarshan* *Associate Tech Lead,* *Data Technologies Team,* *WSO2, Inc. http://wso2.com <http://wso2.com> * *lean.enterprise.middleware.* email: mo...@wso2.com phone:(+94) 771117673
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
