Hi Pradeep, I was looking into the bamdashboard to fix some issues for the latest 2.3.0 release. The issues that you mentioned are still valid apart from the manual config file editing scenario as Chamath mentioned.
We are currently not using UES for the dashboards yet, just our jaggery app. IMO bringing UES into the picture should solve the authentication based concerns. @UES Team can we know if UES is able to support these requirements (auth, multiple dashboard support etc..) and be integrated with BAM. Gokul. On 8 June 2013 09:54, Pradeep Fernando <[email protected]> wrote: > Hi Gokul, > > I believe that, you are the one who looks in to bam dashboard stuff these > days :) . Can you please update the thread with latest development of the > BAMdashboard. (above mentioned issues are invalid with the latest release > ?). > > thanks, > --Pradeep > > > On Fri, May 31, 2013 at 8:55 AM, Srinath Perera <[email protected]> wrote: > >> Are we using UES in BAM yet? will some of the issues go away with UES >> >> BAM team, can we create issues for these please >> >> --Srinath >> >> >> On Wed, May 29, 2013 at 4:17 PM, Pradeep Fernando <[email protected]>wrote: >> >>> Hi, >>> >>> I was working with BAM dashboard for last couple of days. Here are my >>> findings/concerns. >>> >>> 1. Right now dashboard app uses logged in users' credentials for backend >>> access. The proper way to do is, having app-specific credentials. The >>> standard approach is to avoid WS calls altogether and use OSGi services. (I >>> tried to change this, however the logic is written in admin service itself >>> for the tried out scenario) >>> >>> 2. Currently we have to manually edit the config files during each >>> toolbox installation. - Chanaka should be able to explain this further >>> >>> 3. The dashboard pages, do not validate the user(using session) while >>> serving. Hence initial login is somewhat dummy operation. >>> >>> 4. Make login mechanism pluggable - Many users will ask for SSO based >>> login in the future. (since this is different from admin users) >>> >>> 5. Currently logged in user get validated using authenticationAdmin WS. >>> Jaggery now supports user-manager interaction and we can use that. >>> >>> 6. Do we need a permission model (?) >>> >>> listed above are some of the issues (IMPOV) that i came across while >>> working with the bamdashboard. Some of the issues may have got fixed with >>> new release. :) >>> >>> just my 2 cents. >>> >>> thanks, >>> --Pradeep >>> >>> >>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> ============================ >> Srinath Perera, Ph.D. >> http://www.cs.indiana.edu/~hperera/ >> http://srinathsview.blogspot.com/ >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > *Pradeep Fernando* > Member, Management Committee - Platform & Cloud Technologies > Senior Software Engineer;WSO2 Inc.; http://wso2.com > > blog: http://pradeepfernando.blogspot.com > m: +94776603662 > -- *Balakrishnan Gokulakrishnan* Software Engineer, WSO2, Inc.; http://wso2.com Twitter: http://twitter.com/gokulbs Mobile: +94775935789
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
