-
Notifications
You must be signed in to change notification settings - Fork 1
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
Nice product - needs some fixes #1
Comments
Fix for 6 in #5 |
Hi @systemcrash! Thanks a lot for your deep review of our software, we still need to improve on some points but it's nice to hear about the difficulties you have encountered! Problem 1Environment variables need to be written in capital letters, with dashes replaced by underscores (to follow common env vars rules):
It needs clarification in the documentation. Problem 4
It is unclear to me where you can have encounter this In a typical Docker container this variable is not set anyway. I need to investigate. Problem 7The service we host at https://happydomain.org/join is identical to program you have. Each account have its own domains. An ACL system is currently being developed to allow a domain to be shared between several accounts. Each happyDomain instances have its own database containing NS providers information and domains history. Problem 8We support external authentication providers that delivers JWT. It's something we made long time ago so I don't remember all the details but it was designed in order to be compatible with Auth0 and the Ory suite. Others problemsI'll investigate each point you mention. I think that our application has not yet been deployed in enough different configurations. We'll make sure to fix that together. |
Problem 3I was able to reproduce the panic with a Docker image built on the Docker infrastructure, but not with my build, nor with our CI build. Could you please update the Docker image and test again? I disabled Docker autobuilds. With the latest build, I have now:
|
Problem 5Should be fixed in e2e7934. A new option is now available: |
I think Prob 4 was docker trying to use global (host system) instead of the container var. |
I will let you know if I encounter this again. So far so good. |
Hi @systemcrash! We are almost done here, the main point is to document how to use an external identity/authentication provider. Could you test the new |
I just did a I urge you to use Loopias svg logo available. https://www.loopia.com/assets/images/logos/logo-loopia.svg |
I ran from
docker compose
Problem 1:
I could not get it to recognize my config, or its path. So I had to resort to using HAPPYDOMAIN_* ....
Problem 2: even though I use noauth, I am forced to log in. WAT?
provide a bad JWT claims: signature is invalid
Some cookie problem? I want to permanently disable auth if I have to live with the below challenges.
I eventually got around this with firefox and destroyed local cookies for this site.
Problem 3:
I also encountered this traceback, before mail server was configured:
Problem 4:
your docs mention
$XDG_CONFIG_HOME
but what is its default?WARN[0000] The "XDG_CONFIG_HOME" variable is not set. Defaulting to a blank string.
I could not get any of the tried paths for config to work.
Problem 5:
smtp TLS needs an option to DISABLE TLS - our email server has an old cert (certbot was broken by some DNS change...):
unable to SendValidationLink in specialUserOperations: tls: failed to verify certificate: x509: certificate has expired or is not yet valid: current time 2023-02-23T00:04:53Z is after 2021-11-23T12:12:21Z
Problem 6:
I use
fish
, notsh
- so this does not work:(cd ui; npm install)
Problem 7:
It is entirely unclear from the documentation, or the displayed information WHAT HAPPENS when someone registers. Do they register on your domain? On our private domain? Where is the information stored? internally? Unclear...
I have some weird midas touch. Whatever I touch or use, I trigger all bugs known and unknown...
Problem 8:
Other auth providers? how? which?
=======
Anyway, I like the product, and would like to use it more... Good work to get this far!
The text was updated successfully, but these errors were encountered: