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
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to