[Product] Clarity on Employee RCN

[karntrehan]

How is user management going to be done? Are we going to have a core user service? Are we going to use employee RCN as the core user identifier? etc..

Context: https://app.diagrams.net/#G1f7zz7JjoV0fRNv89iufR9Ot7lwpDHpXK

[karntrehan]

There already is a FusionAuth based User Service layer. It behaves as an authentication + user management layer. Similar to the IODC layer mentioned in the diagram. We shall be using that to manage users data. We can query it to get users matching a condition or get info / metadata for a user. RCN will not be used directly.

[aman1esmagico]

@karntrehan what you mean to say is that we will be only using User Servicefor authentication and user management

1. When User is new in our system

The user come to the platform and do authentication through User Service. If user is there, then we get all the data of the user and save it in our user database. If user is not not In User Service, that means he cannot be a part of our system. And all the other data we want to store of the user, our system specific we will be saving in our db only.

2. When User is already present in the system

We will authenticate the user using User Service.

What about admin??

[abhay-samagra]

@karntrehan - Tarento has mentioned about the Sunbird user service. Please also have a look at this. https://lern.sunbird.org/learn/product-and-developer-guide/user-and-org-service

[aman1esmagico]

also we were expecting the assessor mapping with assesse from employee RCN, now where do we get it from