FoF passport, the Laravel passport oauth extension

jmshorb

I have been searching around for awhile, but can't find any answers. Forgive me if I'm looking in the wrong spot! I am trying to figure out how to manipulate the material in the pop-up modal that shows up after logging in with fof/passport. This asks for a username and (in my case) a nickname since I'm using the nickname extension. This is very confusing for our users as they think they have already logged in, and are asking for another username. Is this expected behavior or can it be bypassed by using some identifier from the authenticator? Or pre-fill the fields so that it's not looking like they are registering all over again?

clarkwinkelmann

jmshorb the user "me" endpoint configured with the "Api URL providing user details when authenticated" setting is used as the default registration payload. If you return values that match the Flarum json:api attribute names, then Flarum should use those values and not prompt the user. The attribute names should be username and nickname, directly at the root of the JSON object.

I've never tried with the nickname attribute, but I expect it's also supported through this feature. The actual underlying feature that powers this is part of Flarum. The extension just uses setPayload on the registration state object, pushing the entire Passport API response as the content.

jmshorb

clarkwinkelmann Thanks! I think we had some issue with our CAS system where we may have disabled this in the core of the extension, and that's an issue. I do not need the nickname to be filled out (they can change that whenever anyway!) but seeing a blank 'username' field was causing the confusion.

poVoq

If I set up Laravel Passport itself (not this extension that acts as a Oauth2 client), will it get the user accounts from the Flarum database?

I would like to have Flarum itself act as a Oauth2 provider, similar to this abandoned plugin, but was told it would be possible to do something similar with this here?

KBExit

poVoq From what I understand, you set up Laravel Passport on your server and it acts as the source of truth for user accounts. This extension bridges the Flarum to Laravel Passport. You control the user data on your end and you can synchronize authentication for your users across all other platforms that can utilize Laravel Passport itself as a source of truth for user accounts (including login and registration).

poVoq

Yes, but in that case it wouldn't be the existing Flarum user database of my forum that is acting as the source of truth for the accounts anymore, right?

« Previous Page