Currently, there is one oauth2 consumer in use in Weasyl, and it is used to allow logins to gitlab. However, HOW it was added is (AFAICT) completely undocumented. While one can remove an oauth2 consumer key at the user level (e.g. 'I don't want this one login to continue to be valid for me, thanks)...
There is no method I can find for anyone, let alone a Weasyl admin or director, to add a new oauth2 system method, or remove one that is already in use. I think the one that exists today is simply hard wired into the database. It should be possible for some level of Weasyl staff - probably admins? - to add or remove valid oauth2 consumers.
poVoq
commented
2 years ago
Currently, there is one oauth2 consumer in use in Weasyl, and it is used to allow logins to gitlab. However, HOW it was added is (AFAICT) completely undocumented. While one can remove an oauth2 consumer key at the user level (e.g. 'I don't want this one login to continue to be valid for me, thanks)...