Thanks so much for the reply!
Ah @flancian replied on 2026-02-27 to support@techcare.coop, maybe it got spamcanned?
Again, happy to help hack into that, should be possible to copy the values in the CREDENTIAL table from a known user. Alternatively, it looks like if someone deletes enough credentials relating to the default admin user, it will get recreated from environment variables. Let me know! But, as per below, I don’t think socialcoop.meet.coop was ever using SSO.
I can’t say for sure either, I am/was just going off Wouter’s post that I quoted.
https://socialcoop.meet.coop/signin
Not sure I 100% understand; here’s a meeting link I had made in case that’s helpful https://socialcoop.meet.coop/3wo-yox-z1p-fvt
Here are our docs on it: https://wiki.social.coop/wiki/Adding_New_Users_to_Meet.coop
Members of the CWG ops team are tasked with responding to new signups for meet.coop accounts as part of their oncall responsibilities.
- Sign into socialcoop.meet.coop.
- Click on your username in the top-right part of the page.
- Click on Organization to visit the Admins page.
- Click the green Invite User button.
- Enter the email address(es) of the social.coop member who needs an account.
- Check the “Invited” tab to confirm that they’ve been invited.
No.
If it’s easy, I think this would be a fine short-term measure so at least Socialcoop users can do “something”. But yes the lack of isolation is a bit non-ideal.
Seems like adding https://auth.social.coop as an “Identity provider” on the Meetcoop Keycloak might be less work for everyone? This didn’t exist when we first became Meetcoop members, otherwise I think we might have done that in the first place.