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

Prevent direct connection to docker draw.io instance #171

Open
Luticus opened this issue Jan 13, 2022 · 1 comment
Open

Prevent direct connection to docker draw.io instance #171

Luticus opened this issue Jan 13, 2022 · 1 comment

Comments

@Luticus
Copy link

Luticus commented Jan 13, 2022

drawio

I have a configuration like the one in this image. I'm trying to use my own draw.io instance in a docker container. What I want to know is how to prevent people from bypassing the Nextcloud instance and going straight to the draw.io location? Are there any thoughts on how to achieve that? As it is now, any random internet user can use the docker draw.io without logging in via Nextcloud which isn't desirable.

@Luticus
Copy link
Author

Luticus commented Jan 17, 2022

One thing I have tried is setting up apache url authentication and putting https://user:[email protected] in the Draw.io URL box, but unfortunately when I try to pass the creds that way I get a content security policy error. If I just log into the draw.io instance directly via the draw.example.com url, without directly passing creds, let it prompt me, and manually enter the credentials, then everything works. That's obviously not desirable though as I don't want to bother users with yet another credential to enter, so it would be best if i could pass the credential automatically in the url.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant