https(OAuth) problem solve idea #1373
FixitNOW982
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
DigiKey requires HTTPS redirection when connecting to the API. Resolving this is a very troublesome issue. There are a few methods, the most common being using Tailscale to handle it with MagicDNS or utilizing Nginx's reverse proxy. However, both are complex and annoying solutions that cannot be recommended. So, the idea I would like to suggest is that we could instead embed mkcert to issue our own certificates and use HTTPS as the default connection. We could set the address to localhost by default, but allow it to be changed to https://www.partdb.com. Since it is a local environment anyway and we only need to satisfy Digikey's OAuth approval requirements, I don't think there will be any significant security issues.
Beta Was this translation helpful? Give feedback.
All reactions