Hi, On Wed, May 29, 2013 at 5:40 PM, Chanaka Jayasena <[email protected]> wrote:
> I install a sample toolbox and the experience was grate. But when there > are multiple toolboxes each toolbox should be linked from the Bam > dashboard. The one added later will replace the existing one in the > dashboard. In order to add it again you have to manually edit the > dashboard.xml file. This is ok with the samples provided. But when creating > custom toolboxes each and every toolbox has to be edited in order to work > them with each other. You have to manually add UI logic to few js files as > well. It's grate if we can come up with a better way of doing this. > This will be fixed in 2.3.0. We used that dashboard.xml configuration only in BAM 2.0.1. BAM 2.2.0 supports default toolboxes without editing any configuration or js file(s), only custom toolbox would need to do it. BAM 2.3.0 has the support of creating your own toolbox and adding it without modifying any configuration(s). There is a public jira for this. https://wso2.org/jira/browse/BAM-1155 Thanks, Chamath. > > thanks, > Chanaka > > > 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 >> >> >> > > > -- > Chanaka Jayasena > Senior Software Engineer; WSO2, Inc.; http://wso2.com/ > email: [email protected]; cell: +94 77 785 5565 > blog: http://chanaka3d.blogspot.com > -- _-_-_-_-_-_-_-_-_-_ Thanks & Regards, Chamath. *+94 71 532 0009*
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
