There is no easy automatic fix. We suggest to fix the auth methods
manually for the time being or provide a patch for the mapping.

** Changed in: mahara
       Status: Triaged => Won't Fix

** Changed in: mahara
    Milestone: 23.04.0 => None

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: mahara-contributors
https://bugs.launchpad.net/bugs/2000686

Title:
  LTI 1.1 misaligned auth after 22.10 upgrade

Status in Mahara:
  Won't Fix

Bug description:
  Mahara: 22.10.0
  OS: Linux 20.04
  DB: Postgres
  Browser: n/a

  Post an upgrade from 21.10 to 22.10, the LTI auth for an institution
  is misaligned and users can no longer log in.

  Scenario with LTI integrated Blackboard LMS:
  - In 21.10, create an institution1 with 1 LIT auth "Web services"

  - Created 2 enabled registered external apps:
  1. "Blackboard LTI" <- owner was deleted but still exists (i.e. create app 
then delete user)
  2. "Blackboard LTI Mahara"  <- genuine LTI and owner still exists

  - Crete users in instintution1 with "webservice" auth

  - Upgrde to 22.10

  - All users should be converted to "Blackboard LTI Mahara" as that is
  the valid instance.

  What happens: the users are still linked to the "webservice" auth
  which doesn't have any valid registered apps.

  
  An additional SQL during the upgrade should:
  * update all auth_remote_user records from the old auth to the new auth
  * update all usr records from the old auth to the new auth
  * the old "webservice" auth in the institution should be deleted

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/2000686/+subscriptions


_______________________________________________
Mailing list: https://launchpad.net/~mahara-contributors
Post to     : mahara-contributors@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mahara-contributors
More help   : https://help.launchpad.net/ListHelp

Reply via email to