OIDC/SSO support in the future?

[WirtsLegs]

I am debating adopting timetagger at home but hesitant due to the currently somewhat basic approach to auth.

Is there any interest or intent to directly support OIDC for authentication down the road?

[almarklein]

Are you talking about the self-hosted version or the hosted version? At timetagger.app there is OIDC for Google and Github.

For self-hosting there currently is indeed only a very basic auth implementation, because there's 1001 ways one can implement auth, so it's kindof left as something to add yourself, for now.

[WirtsLegs]

Sorry yeah I guess I didn't clarify

I was referring to the self-hosted version

In the self-hosted scene there really are just 3 types of auth that are super common in my experience

• Http basic (though without needing to set those creds in a config)
• OIDC: really the dominant oke now as more and more people run identity providers at home, and wig generic oidc config you can point it at say google etc as well
• header auth: which you support

Would love to see oidc come to the self-hosted version at some point

[PassionateBytes]

This is indeed a feature worth adding IMO. Many self hosters (myself incuded) prefer the added security and convenience that comes from federated authentication... @WirtsLegs would you mind adding this feature request as an issue on this repo? I won't promise to work on this, but I might in the future get to it.

[WirtsLegs]

This is indeed a feature worth adding IMO. Many self hosters (myself incuded) prefer the added security and convenience that comes from federated authentication... @WirtsLegs would you mind adding this feature request as an issue on this repo? I won't promise to work on this, but I might in the future get to it.

done: #582