** Changed in: mahara
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- please ask
on #mahara-dev or mahara.org
** Changed in: mahara
Milestone: 1.8rc1 = 1.8.0
--
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- please ask
on #mahara-dev or mahara.org forum before
So, while researching some stuff relating to ldapsync, I gained a bit
more insight into how the remote username parent authority work and
work together:
1. The only auth plugins that use remote username are XMLRPC and SAML
(optionally for SAML)
2. These are both services where you *don't* enter
https://reviews.mahara.org/2452
** Changed in: mahara
Status: Fix Committed = In Progress
--
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- please ask
Ah, it was sorta buggy, if you did this:
1. Set up two auth instances that can take an external username
2. Assign a user to one of them, and give them an external username in that
auth.
3. Save.
4. Now, go to the user's account settings page, and switch them to the other
external auth
Even with my latest commits, there's still a bug case on the user edit
screen:
1. Set up two auth instances that can take an external username
2. Navigate to the account settings page for a user and set their external
username with one of these auth instances
3. Now, change their auth setting to
Never mind... on further testing it actually does work, and does give me
the expected result! :) It was actually already written to look up and
store your external username in all the different auth instances, store
them in JS, and swap them in and out as you switch auth instances.
--
You
I added the tag nominatedfeature though it's more like a bug so I can
pick it up for the manual and highlight this change.
** Tags added: nominatedfeature
--
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching
have reworked the patch to fit better with changes in the
admin/user/edit.php that have occurred after initial patch was
submitted.
https://reviews.mahara.org/#/c/2191/4
now the remote auth field should only show if an external auth has been
selected and update the field with existing remote
** Changed in: mahara
Assignee: Jonathan Sharp (jonathans) = Robert Lyon (robertl-9)
--
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contrib members
https://reviews.mahara.org/#/c/2191/
--
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contrib members
https://bugs.launchpad.net/bugs/1160093
Title:
Don't display a remote
change (experimental) pushed
suggested functionality: Mahara should only display a remoteuser value
if the selected authplugin (in the Authentication method dropdown) is
not '... internal'.
If the Authentication method is external then some javascript displays the
'Username for external
** Changed in: mahara
Status: Confirmed = In Progress
** Changed in: mahara
Assignee: (unassigned) = Jonathan Sharp (jonathans)
--
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription
13 matches
Mail list logo
