Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Consideration] Publicly expose server with OAuth2 requests #6

Open
ItzSwirlz opened this issue Aug 30, 2024 · 0 comments
Open

[Consideration] Publicly expose server with OAuth2 requests #6

ItzSwirlz opened this issue Aug 30, 2024 · 0 comments
Labels
enhancement New feature or request help wanted Extra attention is needed question Further information is requested

Comments

@ItzSwirlz
Copy link
Owner

If someone does not have a server that they can run actions to connect smart assistants like Google Assistant to their device, it may be good to just have Ristretto handle OAuth2 so when setting up the action, whoever is doing it can just point everything directly to Ristretto.

However, this would mean that Ristretto's public server would be exposed. Therefore, requiring port forwarding, using something like DuckDNS for a domain, this is really a scenario for which ecosystems do not allow for local servers to be used or if someone does not have access to another device to run their server on.

@ItzSwirlz ItzSwirlz added enhancement New feature or request help wanted Extra attention is needed labels Aug 30, 2024
@ItzSwirlz ItzSwirlz added the question Further information is requested label Sep 16, 2024
@ItzSwirlz ItzSwirlz changed the title [Feature Request] Publicly expose server with OAuth2 requests [Consideration] Publicly expose server with OAuth2 requests Oct 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant