let's consider tenanted URLs after M5. On Tue, Oct 6, 2015 at 1:10 PM, Udara Rathnayake <uda...@wso2.com> wrote:
> Hi Ayesha, > > frankly I haven't tested any tenant scenarios with this implementation. > > *few points to consider* > If user (not authenticated) browses the dashboard > https://<host>:<ip>/portal/dashboards/<dashboard-name> > this should render the anon view. Once user logged in we should render the > default view. In this default view we DON'T need to provide a link to anon > view. (this should be available during the design phase for developer to > review) > > We don't need to think about user level customization within the anon > view(since no real user exists at this time, no edit stuff in anon view). > > I discussed above with Sajith today. > > Regards, > UdaraR > > On Tue, Oct 6, 2015 at 12:56 PM, Ayesha Dissanayaka <aye...@wso2.com> > wrote: > >> Hi Udara/Manu, >> >> Have we considered multi-tenant scenarios while designing anonymous view >> of dashboards. >> >> For instance what will be the dashboard view rendered for an user who has >> logged into super tenant and trying to access a dashboard view URL of >> another tenant domain.( ex. wso2.com). >> >> In that case should we still show the anonymous view of the dashboard or >> default view? >> >> In my opinion we should show the anonymous view and disable the dashboard >> edit options. WDYT? >> >> Thanks! >> -Ayesha >> >> >> On Fri, Oct 2, 2015 at 6:43 PM, Udara Rathnayake <uda...@wso2.com> wrote: >> >>> Thanks for the feedback lasantha and nipuna. >>> I'm +1 to make the landing page anon if there are any anon views defined >>> in other pages. Let's stick to that. >>> >>> On Fri, Oct 2, 2015 at 9:15 AM, Nipuna Chandradasa <nipu...@wso2.com> >>> wrote: >>> >>>> Hi Udara, >>>> >>>> As Lasantha said that making the landing page an anon view should be >>>> mandatory if there are anon views available under the that landing page >>>> even the landing page doesn't have anon content to view. >>>> >>>> I think this is a good idea because it is not that great to have child >>>> pages which has anon view but the user cannot access the main view. At >>>> Least if there are no content to show under the landing page to a user ( >>>> Which is not that great if it mandatory to make the landing page anon view) >>>> at least we can show a message saying which pages are anon views and have >>>> the anon content. >>>> >>>> Thanks. >>>> >>>> On Fri, Oct 2, 2015 at 8:46 AM, Lasantha Samarakoon <lasant...@wso2.com >>>> > wrote: >>>> >>>>> Hi Udara, >>>>> >>>>> Can't we show the actual landing page even though the anon view is not >>>>> defined? So if the landing page doesn't have a anon view, then we can show >>>>> some message with all other links to accessible pages (Same as what we >>>>> have >>>>> in regular websites. Once you logged in you have more features, otherwise >>>>> limited. But the home page is home page). >>>>> >>>>> In your first option, the problem is that if the developer couldn't >>>>> define the anon view landing page, ultimately the dashboard is not >>>>> accessible for any anon user unless he knows the direct url for a page. >>>>> Then there's no point of introducing the anon view for such scenarios. >>>>> >>>>> In the second option, as you mentioned it actually breaks the concept >>>>> behind a landing page. And know one can define what will be the actual >>>>> landing page in such situation. >>>>> >>>>> Or else we can emphasis (or make it mandatory) the developer to define >>>>> a anon view for the landing page in the designer if there are any anon >>>>> pages for the dashboard. >>>>> >>>>> >>>>> Regards, >>>>> >>>>> >>>>> *Lasantha Samarakoon* | Software Engineer >>>>> WSO2, Inc. >>>>> #20, Palm Grove, Colombo 03, Sri Lanka >>>>> Mobile: +94 (71) 214 1576 >>>>> Email: lasant...@wso2.com >>>>> Web: www.wso2.com >>>>> >>>>> lean . enterprise . middleware >>>>> >>>>> On Thu, Oct 1, 2015 at 8:10 PM, Udara Rathnayake <uda...@wso2.com> >>>>> wrote: >>>>> >>>>>> Hi All, >>>>>> >>>>>> At the moment we have a landing page (which developer can select >>>>>> while creating the dashboard) and this is the page end-user will >>>>>> initially >>>>>> get once he/she browse the dashboard. >>>>>> >>>>>> So for the anonymous view of the dashboard, we are going to use the >>>>>> same landing page's anon view(if exists) else user will be redirected to >>>>>> the login page. >>>>>> This approach will basically need developer to have a anon view >>>>>> within the landing page if there are anon views for other pages. >>>>>> >>>>>> Otherwise we can go through existing pages and check existence of >>>>>> anon views first and then render. This approach will deviate from the >>>>>> landing page concept a bit. >>>>>> >>>>>> Any thoughts? >>>>>> >>>>>> Regards, >>>>>> UdaraR >>>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Dev mailing list >>>>> Dev@wso2.org >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> Nipuna Marcus >>>> *Software Engineer* >>>> WSO2 Inc. >>>> http://wso2.com/ - "lean . enterprise . middleware" >>>> Mobile : +94 (0) 713 667906 >>>> nipu...@wso2.com >>>> >>> >>> >>> _______________________________________________ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> *Ayesha Dissanayaka* >> Software Engineer, >> WSO2, Inc : http://wso2.com >> <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> >> 20, Palmgrove Avenue, Colombo 3 >> E-Mail: aye...@wso2.com <ayshsa...@gmail.com> >> > > -- With regards, *Manu*ranga Perera. phone : 071 7 70 20 50 mail : m...@wso2.com
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
