With SSO for major services, it might actually be much easier to fork sso-github or similar, instead. Reason being there sometimes are npm packages that help you log in to these services.
Then you can really just change the require from github to gitlab, and hopefully it would just work.
Almost all of the time it actually won't be that easy, but it sure beats doing it from the sso-oauth base!
In case anyone decides to work on that topic: I would really love to see a light version of the Teamspeak widget, that is, without detailed information on clients.
The reason is that I have to deal with a very restrictive rented Teamspeak server where ServerQueries are limited to 10 per 3 seconds (no possibilty to add domains to the whitelist).
Two requests, one for clientlist and one for channellist, would be enough to create a basic viewer layout.
Also, caching the requests so that multiple concurrent page views don't trigger a server flood alert would be great.
I had a look at the widget from @pitaj, but unfortunately my programming skills are rather low.