Open ID for auth, secondary system for user sync?

Re: Open ID for auth, secondary system for user sync?

by Nelson Bartley -
Number of replies: 2

So funny enough, that's exactly what I understood of the system. The current oath2 plugin apparently supports connectid and jwt, so that's the easy part.


The problem is, that means the users all have to login once before they exist in the system. This is not good for class management. What I want to know is how I register all my users into the system before hand and either map them to a connectID or when they finally log in have the connect id auto map to the user already registered.





In reply to Nelson Bartley

Re: Open ID for auth, secondary system for user sync?

by Werner Visser -

Hi Nelson,


Did you manage to figure this out?  We similarly would like to register users via a service and automatically log them into Moodle from our app so that the experience is seamless.


Would love to hear from you and if you have a solution?


Thanks

In reply to Werner Visser

Re: Open ID for auth, secondary system for user sync?

by Nelson Bartley -

No I didn't, and there was minimal involvement from the community.