search

aptabase / self-hosting

Configuration and Documentation for Self-Hosting Aptabase
36 stars 9 forks source link

Cannot seem to implement authentication #2

Open ChickenBone opened 1 year ago

ChickenBone commented 1 year ago

Hello, I have been trying to improve on the default "Magic Link" system that is in place and I noticed the option to include GitHub OAuth credentials. I setup the environment variables and restarted the container but cannot seem to find a way to get signin with GitHub.

The main issue is just the internal UX of the magic link method. if there is any easy way to override the authentication or implement a secondary method please let me know!

Thank you!

goenning commented 1 year ago

What issue did you have with magic links?

If it’s related to the email, you can leave all the SMTP env variables empty and look at your container logs as the magic link is written to stdout when there’s no email server configured.

Handy if you’re the only one who would need to access the server.

What issue did you have with GH OAuth? Maybe I should document that part too

ChickenBone commented 1 year ago

Hey thank you so much for replying! The issue I ran into with SMTP is simply just a ux issue. We will have multiple people accessing the panel and SMTP just isn’t the best solution for us. Along with the GitHub oauth I just can’t seem to get it to work or appear period. I added the ENV variables and setup the callback url for GitHub’s side but still no sign in with GitHub button on the sign in screen.

(edit) We have these env variables OAUTH_GITHUB_CLIENT_ID OAUTH_GITHUB_CLIENT_SECRET

Thank you!