You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to run journalctl-proxy on a publicly accessible server, but would like to restrict access to authorized users. Forks have provided Basic HTTP support, which is better than nothing, but would like to extend this specifically to SSO authentication from an OAuth provider (Google, etc).
The text was updated successfully, but these errors were encountered:
@kylemallory This is an interesting option. SSO is not difficult to add, but the setup on your side would be more complicated. You would need to create apps for Google etc and then also provide return IP's or domain address to validate if login was successful. This is maybe too complicated for a utility like that.
The only reason I would see this valuable would be for users to gather emails of people that accessed this.
Basic auth is a good option. I need to add this for sure.
I'd like to run journalctl-proxy on a publicly accessible server, but would like to restrict access to authorized users. Forks have provided Basic HTTP support, which is better than nothing, but would like to extend this specifically to SSO authentication from an OAuth provider (Google, etc).
The text was updated successfully, but these errors were encountered: