Hi Hasini, On Mon, Jan 23, 2012 at 10:06 PM, Hasini Gunasinghe <has...@wso2.com> wrote:
> Hi Senaka, > > On Mon, Jan 23, 2012 at 8:41 PM, Senaka Fernando <sen...@wso2.com> wrote: > >> Hi Azeez, >> >> Sorry lost track of this. >> >> 1. The first one is the easiest. Insert malformed XML into user-mgt.xml >> and start the server. Console is clean (no exceptions). Server hangs and >> does not start-up. There is no clue to what went wrong. Just make >> <Configuration> into <!--Configuration>. >> > > Error reporting needs to be fixed here. Thanks for reporting. > > >> 2. Create any possible error that would result in the user profiles >> section being corrupted. No exceptions on the BE. The front-end returns the >> same error message for all types of errors making debugging a nightmare. We >> reproduced this by a an accidentally corrupted database, but there could be >> many other ways to get to this. > > > I couldn't reproduce this with user profiles feature. Can you please > mention couple of examples out of the many ways you observed this? > As I said I got it reproduced using an accidentally corrupted DB, but there could be many other ways - by looking at the code. But, I have not attempted to. What I'm trying to get to is that, any error will produce no stack traces but a single error message in the UI. > >> Though not quite related, we noticed that usernames on Carbon 3.2.3 are >> case-sensitive, > > > I guess you meant to say case insensitive - we have mentioned this in > sign-in help docs as follows: > > "*Please note that due to the inherited behaviour of default user store - > which is embedded-ldap, user names are case insensitive in 3.2.0 based > carbon products*." > > Are you sure the login failure you encountered is due to a case sensitive > issue? > Because username is case insensitive as mentioned above - and allows you > to login even if you change the case of the username. > Actually, if the username was 'U12345' you cannot login as 'u12345', which is the concern. Thanks, Senaka. > > Thanks, > Hasini. > > >> which is a L1 regression. Also, just as in 1 and 2 above, the error is >> failed login attempt, and BE is dead silent to what went wrong. It took at >> least a dozen retries to figure out and a fair amount on time wasted in >> understanding what went wrong. Though the FE might give out a simple >> authentication failure, I'd expect the BE to be more specific to what went >> wrong. >> >> Thanks, >> Senaka. >> >> >> On Mon, Jan 23, 2012 at 8:19 PM, Afkham Azeez <az...@wso2.com> wrote: >> >>> Please post the relevant code segments. This is something we keep >>> repeating during code reviews. >>> >>> On Fri, Jan 20, 2012 at 11:16 PM, Senaka Fernando <sen...@wso2.com>wrote: >>> >>>> Hi all, >>>> >>>> Just like it can be ugly to see lengthy stacktraces at times, seeing >>>> the UI not working and errors throwing and no stacktrace or clue of what >>>> went wrong is extremely annoying. I was getting some errors from UM this >>>> time, and multiple kinds of it; and, had to debug the code to learn what >>>> was going wrong. The server is failing to work, but the console and the FE >>>> has no clue to what went wrong. It's greatly appreciated if we could go >>>> through some of these code and check that we properly throw exceptions. I >>>> will follow up on the instances where exceptions were not thrown and how to >>>> reproduce them. >>>> >>>> Thanks, >>>> Senaka. >>>> >>>> -- >>>> *Senaka Fernando* >>>> Product Manager - WSO2 Governance Registry; >>>> Associate Technical Lead; WSO2 Inc.; http://wso2.com* >>>> Member; Apache Software Foundation; http://apache.org >>>> >>>> E-mail: senaka AT wso2.com >>>> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 >>>> Linked-In: http://linkedin.com/in/senakafernando >>>> >>>> *Lean . Enterprise . Middleware >>>> >>>> >>>> _______________________________________________ >>>> Carbon-dev mailing list >>>> Carbon-dev@wso2.org >>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>>> >>>> >>> >>> >>> -- >>> *Afkham Azeez* >>> Director of Architecture; WSO2, Inc.; http://wso2.com >>> Member; Apache Software Foundation; http://www.apache.org/ >>> * <http://www.apache.org/>** >>> email: **az...@wso2.com* <az...@wso2.com>* cell: +94 77 3320919 >>> blog: **http://blog.afkham.org* <http://blog.afkham.org>* >>> twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> >>> * >>> linked-in: **http://lk.linkedin.com/in/afkhamazeez* >>> >>> * >>> * >>> *Lean . Enterprise . Middleware* >>> >>> >>> _______________________________________________ >>> Carbon-dev mailing list >>> Carbon-dev@wso2.org >>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> >>> >> >> >> -- >> *Senaka Fernando* >> Product Manager - WSO2 Governance Registry; >> Associate Technical Lead; WSO2 Inc.; http://wso2.com* >> Member; Apache Software Foundation; http://apache.org >> >> E-mail: senaka AT wso2.com >> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 >> Linked-In: http://linkedin.com/in/senakafernando >> >> *Lean . Enterprise . Middleware >> >> >> _______________________________________________ >> Carbon-dev mailing list >> Carbon-dev@wso2.org >> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> > > _______________________________________________ > Carbon-dev mailing list > Carbon-dev@wso2.org > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- *Senaka Fernando* Product Manager - WSO2 Governance Registry; Associate Technical Lead; WSO2 Inc.; http://wso2.com* Member; Apache Software Foundation; http://apache.org E-mail: senaka AT wso2.com **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 Linked-In: http://linkedin.com/in/senakafernando *Lean . Enterprise . Middleware
_______________________________________________ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
