Feature Request: Invitations about symfony-demo-app

[ro0NL]

Hi @tacman i think i solved a similar use case in the demo app with "one-time-login tokens".

See #62 for the initial changeset

Conceptually you cannot register a new user by invitation code, and at the same time store the code with a user. In that case the user is already considered registered.

So alternatively you could create a list of invitation codes, and couple it with the created user after registration. But maybe you're just looking for one-time-login tokens :D

[ro0NL]

From the example at https://symfony.com/doc/current/bundles/FOSUserBundle/adding_invitation_registration.html , im not sure how it works ... Where is the user created from an invitation? Or does it assume the users already exist beforehand 🤔 (maybe FOS does it somewhere?)

[tacman]

Invitations contain the one-time login token, along with an optional blob of pre-defined data (e..g ROLE_ADMIN, or their name/organization if that is known when the invitation is created). When the invitation is sent, there's a link with ?ic=<inviationCode>, which goes to the registration page. Quite possible to use all of that logic and simply redirect the link to the user-bundle login page, as you've done. I'm working on a demo app/tutorial that is based on your demo app but adds some real-world content. I'll try to get invitations working, then we can figure out if it makes sense to include that in your bundle's core.

…

On Mon, Jul 8, 2019 at 10:50 AM Roland Franssen ***@***.***> wrote: From the example at https://symfony.com/doc/current/bundles/FOSUserBundle/adding_invitation_registration.html , im not sure how it works? Where is the user created from an invition? Or does it assumes the users already exists beforehand 🤔 (maybe FOS does it somewhere?) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <https://github.com/msgphp/msgphp/issues/336?email_source=notifications&email_token=AAEXIQPGIZ2LI5ZITJIJ5ZDP6NHZXA5CNFSM4H632L7KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZNKP2A#issuecomment-509257704>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAEXIQMTA32RGMAU47BCKR3P6NHZXANCNFSM4H632L7A> .

[ro0NL]

Maybe we can enhance the demo as such :) i tend to keep pure business logic (opinionated) out of core bundles.

Hence the demo defines it's own one-time-login console command, entities etc. All linked to the "core" User domain.

I think we're dealing with 2 distinct concepts;

• one-time-login token
  • bound to an existing user
  • allows to login
• invitations
  • bound to an existing user post registration
  • allows to register with pre-defined fields