Weblate OIDC migration #12479
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I've just learned from https://github.com/python-social-auth/social-core/pull/1099 by @abompard that is a plan to drop OpenID in favor of OIDC.
https://translate.fedoraproject.org/ is still using OpenID, so some actions need to be taken to migrate to OIDC.
To be able to use OIDC in Weblate, https://github.com/python-social-auth/social-core/pull/1099 first will need to be merged and released.
Is there some documentation on migrating user associations? Or will the identifiers stay look like with OpenID?
CC @jibecfed
Metadata Update from @zlopez:
From what I heard from @abompard it should be able to link the openid accounts to OIDC ones.
But I leave this for @abompard to answer.
Hey! In python-social-auth, there is a setting called
SOCIAL_AUTH_PIPELINE
where you can list functions that will be run during the authentication process. Thesocial_core.pipeline.social_auth.associate_by_email
function is disabled by default, but if you enable it it will match by email address logging-in users with existing users. As a result, new users using OIDC will get their existing account, if you have enabled this function in your pipeline.I think one of the issue is that translate is a hosted service.
I met with @jibecfed this weekend who pointed me to @darknao for technical matters wrt weblate hosted instance.