Now, let's talk about how to resolve the issue if you have a user who has been merged in your AMS and then have problem logging in. We have created an example that's actually a real case. So I'm just going to use a real case to highlight exactly what the data looks like. So prior to the merge, there are two accounts in the system for the user Bezos address. And the first one I'm going to show here, okay, which is going to put my browser a little bit lower to show exactly how the user account is laid out. We have one account that is, this is referred to as Oasis ID, is 121085, which is the first one. This is the name of the account, this is the email address, and this is the ID, right? Perfect. And then there is another account, Oasis ID is 22188. And then you will see that the person's email is marshall.edu is their new email and HRS ID is the member ID here. So before the merge, there are two accounts for Bezos address. Now, once the user is merged, what happens is the user will log in with this credential and notice what the first thing Oasis does is Oasis is going to say, oh, I see this is your member ID. So I'm going to try to log you in as user A because that is the matching member ID. But I also noticed that your email address have changed. So I'm going to say, oh, this is your email address. I'm going to update your hotmail to this. Like I said in the earlier video, Oasis require unique email address, and then it's going to fail at logging in the user C because when I try to, when I find the user by the same member ID and try to update the email address, there's already someone else with the same email address. And to highlight that actually happened, I'm going to go to this account 21085, which is the one that we're trying to log in as when the user C come in. I go to user log. If I search for fail, you will see that constantly when the user tried to log in, it has failed. It has failed because this email address has been used by someone else. By who? By user B. So this is why when the merged account tried to log in, it continued to fail. Now, to fix the problem is actually fairly easy. All you have to do is go to tools, user, merge user account. And then what you do is we recommend to avoid ambiguity. You grab the Oasis ID here, and then you basically say, I'm going to merge user account B. I'm going to merge into user account A. Exactly which one is merged from and which one is merged to is a little bit of art than science. We recommend looking for a user who has the least amount of content that they have done. So you can see here, they both have done quite a bit. So this is going to be a really big toss up on exactly which one you want to merge from and which one you want to merge to. The reason you have to make a decision is if there are courses that's taken by both, then the courses that merge source or merge from has taken is going to be deleted. If any courses that's only taken by one or the other, then after the merge, whoever is left over will have a combination of all the courses. But with that said, if I perform a merge like what I'm showing here, what will happen is user B will be deleted. I'm going to delete that, but then all the progress made on user A will be part of all the progress that was under user B will be part of user A. Now when the user C logs in, notice that we're going to say, oh, I find the account under user A and I see the email address that's Marshall. I'm just going to update user A with the new email address. So this is how you will merge account. But like I said, exactly which account is merged from to which account, you have to make a judgment call, and that is difficult for OASIS to make a decision. There are cases where it's easy to make a decision. In this case, you notice that the user actually have a third account that has never been logged in. Then, you know for sure this is basically created as a byproduct of something else, such as a bulk import or some sort of a menu creation. Then what you can do is you can definitely delete this account or merge it into another account that's actually being used. Thank you.

login issues

merging user accounts

AMS

email address uniqueness

merging process

SSO

Single Sign On

SSO issue

surabaya