On Thu, Oct 10, 2013 at 11:50 AM, Asela Pathberiya <[email protected]> wrote:
> > On Tue, Sep 24, 2013 at 11:39 AM, Venura Kahawala <[email protected]> wrote: > >> Hi, >> >> We are in the process of moving the below UI features out from the IS >> management console. >> >> 1. My Profiles >> 2. Account Recovery >> 3. My Authorized apps >> 4. OpenID >> 5. My SCIM Providers >> 6. Multifactor Authentication >> 7. Sign-up >> > > 8. Password change by user > > >> >> >> A jaggery application will be implemented with the above mentioned >> features and deployed within IS server. This application can be accessed >> via a different port. High level architecture diagram can be seen here [1]. >> >> Jaggery application will be implemented ad-hearing to the caramel >> framework. >> >> [1] >> https://docs.google.com/a/wso2.com/drawings/d/1jQsKbSVnH3cHCKkNjaLqr9cBARk0pD04RLPGgid4R7M/edit?usp=sharing >> >> Please share your thoughts. >> > > +1 for having this without OSGI... It is better to use web services as > you have mentioned. > > Also, is there any special reason for using Jaggery? Because , i see that > web app that you are developing would not be much portable. Actually in a > practical situation, i may have already developed web application that is > running on an app server. Then i need to enable some identity management > features (account recovery, change password, signup) in to my exiting web > app. Therefore i would add presentation pages for this using exiting > presentation layer. So i would look for some client side library to call > these web service APIs of Identity Server (I would not look for already > developed Jaggery app). I guess, it is to better to have some kind of > client side sample library where we could use to develop my presentation > pages. If we can write this Jaggery web application using kind of client > side APIs, that would be fine. If not, I do not think there is much worth > of this for the developers who are using Identity Server's APIs. However > it would just add some nice UI pages to WSO2 Identity Server. (when it is > developed in cloud) > +1, yes, if you can have a common client library, people can write their own UIs/pages in jsp / jaggery. by default IS can have a jaggery app, but should separate the client library, so that it can be reused. we have done it at [1] and [2] is the common client library [1] https://github.com/wso2/enterprise-store/tree/master/modules/apps/sso [2] https://github.com/wso2/enterprise-store/tree/master/modules/components/sso-common > > Thanks, > Asela. > > > >> >> Regards, >> Venura >> >> -- >> Senior Software Engineer >> >> Mobile: +94 71 82 300 20 >> >> > > > -- > Thanks & Regards, > Asela > > ATL > Mobile : +94 777 625 933 > -- *Thanks & Regards, Nuwan Bandara Technical Lead; **WSO2 Inc. * *lean . enterprise . middleware | http://wso2.com * *blog : http://nuwanbando.com; email: [email protected]; phone: +94 11 214 5345 * <http://www.nuwanbando.com/>
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
