Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

This issue can't be edited

Because it belongs to an archived project. Jira admins can restore projects from the archive.

AILP - while Sign up using portal solution, the user is not associated with the root org and channel

Description

For AILP sunbird instance aiprohub.org, when we signup as a new user through the portal, we could see that the user is not associated with the AILP instance's proper root org and channel. The user is assigned the default root org and channel. We would want the new user to be associated with the correct(AILP's) root org and channel so that the user is able to view/browse/enroll/consume courses only in Julia instance.

Can you pls fix this issue. Pls let us know if you need any further info.

Thanks,
Thillai.

Environment

None

Design Document

None

Activity

Show:

Mohit GargDecember 28, 2018 at 4:41 AM

can you close the bug?

Manzarul HaqueSeptember 11, 2018 at 4:55 AM
Edited

Solution for this issue is as follow:

  1. if channel is passed in request body then that need to be validated

  2. if channel is not passed in request body then it will read custodian root org , which will be set inside system setting table during system init script.

  3. if custodian rootOrg is not set then it will try to read channel value from env (as fallback)

  4. User and rootOrg mapping

All the above points are applicable for user/v1/create api.

A newer version of create user v2 is introduced, where channel is mandatory parameter in request body and they can pass organisationId as well (optional) . in that case user and org associated will happen for both rootOrg and passed organisationId.

cc:

Shailesh KochharAugust 2, 2018 at 8:34 AM

let's consider this item in the context of reducing the use of default root org/channel till we can eliminate it. Please create a task to identify the areas where default org/channel are being used.

cc: ,

Manzarul HaqueAugust 2, 2018 at 8:09 AM

As per my understanding you need below changes.
1. If System won't have any RootOrg then user creation should fail.
2. If System having only one RootOrg the user should be associated with that RootOrg
3. If System having multiple RootOrg then in user creation channel need to be passed .
4. Creating tenant specific pages to set channel values during signup.
Can we have a discussion today to agree on above points.
cc:

Rayulu VillaJuly 18, 2018 at 10:22 AM

Please plan for a design review of this for 1.10.0 release and plan to close this in 1.10.0.

Done
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Severity

S2

Priority

Sprint

Labels

Components

Module

Sunbird Platform

Affects

500Kai

Affects versions

Week #

Week 1

Original estimate

Time tracking

2d 5h logged1w 4d 7h remaining

Demoable ?

Yes

Dependencies

Yes

Design Review Completed?

Yes

Coding Complete?

Yes

Design Required?

Yes

Docs Required?

Yes

Documentation completed?

Yes

Reporter

Fix versions

Invision for Jira

Created April 10, 2018 at 12:07 PM
Updated January 12, 2019 at 11:33 AM
Resolved January 12, 2019 at 11:33 AM