Improve authentication methods & docker setup #1177
Comments
|
Looks like the pull #1088 which allows logging in with email accounts was already merged. But it only allows one to add guests who doesn't have google/slack and not to setup the whole thing without those. This is a really stupid decision for an open source software to take tbh. It should be as simple as :
|
What kind of help do you think should exist for running the docker container outside of that already in the README?
Would accept a PR for this. At that point I think we'd have to separate the production and development docker files. Right now the one published on dockerhub is the same as used for dev.
You don't need an env file currently, it's just a convenience. |
|
Being able to use a simple email / password combo to sign up would make me able to use the project, and I'm sure there are a lot of people in my situation.
edit: I've created a Slack organization, see what I can do with it |
|
@Araly the development setup is fairly straightfoward. However the best case scenario for production would be something like: then get a screen that asks for a username and password, and done, you're in. |
|
I wanted to understand if there has been any movement on this. We are actively using a self-hosted outline (dockerized), but now we are moving out of google auth to Onelogin auth (as an org). Now, I am stuck thinking about what to do here. I cannot use slack as a means to login into outline. Any suggestions? Just updated the docker image to the latest tag (0.41.0), but still stuck :/ |
|
There has been some movement on the branch at #1183 – once the auth library is moved over it should make the addition of new authentication methods much simpler. |
|
I had issues installing Outline in my traefik docker setup, so I moved to Nextcloud for the use I wanted of it. Maybe later I'll come back, but for now Outline is too complicated (needing s3 for storage, slack for logging, I was having issues actually logging in at all) |
|
s3 storage is very easy to get setup, you just need a basic IAM role with S3 access that you can give to outline. the usage should fall within the AWS free tier or only cost you cents on the dollar. you dont need slack for signin, you can setup google signin easily enough. the docker image at this time runs all in all outline is very easy to setup with docker. if you're struggling perhaps you should look at a paid version instead? you don't need the The docker image you pointed to work perfectly fine (from my experience atleast). I think you should take another look to ensure you haven't missed anything in the process. |
|
Reiterating my original sentiment. Outline is too good to not be able to run without any additional integrations. |
|
@arjunv using s3 / google / slack does make sense in early development stages as you don't have to deal with managing password reset, email verification, storage, etc. But once you bring your product to market, email / password is a must have if you don't want to constraint your users. That said, there has been tremendous progress with #1183 which is targeted for August/September so I think we just have to wait now 😄
I think you're missing the point of this issue here. |
|
Update, as of version v0.45.0 there is no longer a build step on docker startup. |
|
Authentication without Google or Slack would be a great benefit to me! Outline looks great but my projects do not use gsuite or Slack, so we are unable to use Outline. |
|
When can we expect that outline supports simple mail login? Only with this requirement we could use it in our company. |
|
I'd love to use Outline for my organization, as well, and am unable to, so long as Google, Slack, or any other sub-optimal-privacy authentication options are the only ones available. |
|
Thanks for filing this @gempain – I'm going to close this issue now, it's been a year since it was filed and there has been significant progress on the individual points in the original description, of particular note:
There is another more specific issue here for local authentication that I'd point folks interested in that to: #1881 |
|
@tommoor thanks a lot for following up on this. I've now been using outline daily for a year and it's a real pleasure to write in it. Thanks for your great work ! |
Uh oh!
There was an error while loading. Please reload this page.
Hi there,
First, I'd like to say that I tried your wiki with a local install and I loved the experience, really, truly graceful and beautifully designed - kind of has a feeling of Ghost.
I am a bit disappointed that at almost 8k stars, the only way to authenticate is Slack. I would expect email auth first, then cool stuff like Slack. I'd also love to see things like Mattermost, which is a self hosted Slack clone. Storage wise, I'm fine with AS3 because there is a fake AS3 image that we can use as an alternative. Slack, however, can't be swapped.
I've seen issues/PRs on this repo trying to integrate various authentication mechanisms, and I think adding them would really boost adoption of this project. Six months ago, what stopped us from using Outline internally was a lack of authentication mechanisms and ease of docker setup.
In our case, we use Mattermost as a self-hosted Slack alternative. I gave a shot at writing the Mattermost integration, but it seems that the current project structure isn't really friendly for adding new authentication mechanisms, so I gave up.
Docker wise, it's getting there, but I feel like it's still too complex. Users should be able to spin up an outline instance in 5 minutes on any Docker-compatible machine, without having to clone, install dependencies, create a
.env, etc. I would suggest:yarn installbut can't be sure of what it really does and how to use the image). For this, just package node_modules with your Dockerfile, or bundle them with webpack..envfile, just provide those values as Docker environment variablesYou've got awesome features and a great UI/UX, but the devX and sysadminX isn't so smooth, but I'm looking forward to seeing this project grow.
Keep up the great work !
The text was updated successfully, but these errors were encountered: