New user has no rights on project after invitation on Taiga 6

[niwo]

Hi,

I'm experiencing an issue with taiga-contrib-openid-auth on a Taiga 6.0.7 installation.

Behavior
A user which has no existing account is added to a project and receives an invitation to join.
If the user creates an account through the sign-up form everything works as expected.
If the user logs in through OpenID (for the fist time) the account ist created, but the user has no rights on the project he has been invited to and the invitation is still pending.

Environment

• taiga-back 6.0.7 with taiga-contrib-openid-auth 6.0.7
• taiga-front 6.0.7 with taiga-contrib-openid-auth 6.0.7

[robrotheram]

Just to check there is a env variable PUBLIC_REGISTER_ENABLED I think by default it is set to false.
if you add PUBLIC_REGISTER_ENABLED=True if the user is not in taiga they will be automatically registered if set to false then they are not, but you should get a error saying registrations have been disabled.

[niwo]

Thanks @robrotheram !

Yes, I did set PUBLIC_REGISTER_ENABLED=True. I already noticed that this behavior changed and added this env variable.
Without this setting, the openid-auth module will throw the error as you describe.

The issue which persists is with the project associations: After account creation the user is NOT associated with the project he has been invited to, which is not the expected behavior in my opinion.

[michzimny]

I'm having the same issue. An invited user can log in (register), but they are not added to the project.

[PaulRostecki]

I had the same problem. An invited user could register, but they were not added to the project.
For me, the problem was that openid_login_func in services.py file in back, never received token that is required to associate user with the project he has been invited to.
I worked around this issue by getting token from the invitation url, that is passed to openid_login_func in redirect_uri. Invitation url actually contains the token in its path.