2

I'm working on an SSO implementation where I have to give access to a Drupal 7 site to external users authorized/authenticated by Oauth2. I'm struggling with the process of taking the supplied user information from the Oauth2 server and creating a drupal user from that.

As I understand the application flow

  1. Using an authorization grant flow, users are redirected to external oauth2 server for authentication, server responds with authorization code and scope
  2. Drupal 7 site takes authorization code and forms post for authorization token.
  3. Auth token is used to get user info.
  4. User info is processed from JSON, formatted to array, and then fed into user_external_login_register, success!

Looking at the documentation the user_external_login_register page it looks like the user object needs to be provided a password. What should that be since in an Oauth2 scenario the D7 client site shouldn't have access to the user's password?

It also looks like the two examples assume that some of the credentials are being supplied and processed by the user login form. In my case all of the credentials are being supplied by an API and no drupal form is being submitted. How do I shape this to my use needs? Or, do I need to create a second form that gets submitted programmatically?

Finally, the native user base has many required fields to register and required admin approval on registration. I don't need that info for the external users, and the users don't need to be approved, they should just get logged in.

In theory, there are two general login flows. The first is a self-initiated authentication against the Oauth2 server; the second the user is redirected and authenticated from the partner organization site. Either way, my logic begins when the auth code get provided to the site.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.