Hi Prabath, AFAIK there are a few concerns regarding this. For instance the publisher and store authenticate users with the Key Manager using Web services and the web service URLs are configured in api-manager.xml. So we need to install some APIM components to get this done.
Also since APIM uses the config registry to store some metadata, there are concerns on how to deploy the store/publisher app in a AS cluster. On Wed, Oct 9, 2013 at 10:18 PM, Prabath Siriwardena <[email protected]>wrote: > How do we do this inAPI - Store / Publisher ? Can we host the API Store / > Publisher in a different Application Server and still points to the same > user base behind the API Manager..? > > Thanks & regards, > -Prabath > > > On Wed, Oct 9, 2013 at 7:32 PM, Venura Kahawala <[email protected]> wrote: > >> Hi, >> >> I'm now implementing the log in functionality for the My-Identity app. As >> per my understanding current user management functionality implemented >> within jaggery uses OSGI services. This is correct if the mentioned >> application is only deployed within the IS server and therefore my-identity >> app is connected to the same user store as the IS. But if we deploy the >> application within an AS, the scenario might be different. >> >> This is also acceptable if the AS and IS both connects to the same user >> store. But in some scenarios these two server might not be connected to >> the same user store. >> For example, IS and user store is located within the internal network >> while AS is located outside the internal network and AS is not connected to >> the internal user store. But still we need to deploy the my-identity app >> within the AS since this application is exposed to the end users. >> >> If we need our application to cater above requirement we need to >> implement the log in functionality using web services. >> >> Please correct me if I'm wrong. >> >> Regards, >> Venura >> >> >> >> 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 >>> >>> >>> 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. >>> >>> Regards, >>> Venura >>> >>> -- >>> Senior Software Engineer >>> >>> Mobile: +94 71 82 300 20 >>> >>> >> >> >> -- >> Senior Software Engineer >> >> Mobile: +94 71 82 300 20 >> >> > > > -- > Thanks & Regards, > Prabath > > Mobile : +94 71 809 6732 > > http://blog.facilelogin.com > http://RampartFAQ.com > -- Thanks & Regards, *Johann Dilantha Nallathamby* Senior Software Engineer Integration Technologies Team WSO2, Inc. lean.enterprise.middleware Mobile - *+94777776950* Blog - *http://nallaa.wordpress.com*
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
