Skip to content
This repository has been archived by the owner on Jun 21, 2022. It is now read-only.

Authentication Problems #2

Closed
jessepmsi opened this issue Dec 8, 2014 · 3 comments
Closed

Authentication Problems #2

jessepmsi opened this issue Dec 8, 2014 · 3 comments
Assignees
Labels

Comments

@jessepmsi
Copy link

I have followed the instructions, and have launched this stack both in a private VPC and a public VPC.

No matter what I do though I get an unauthorized message when I try and navigate to the Kibana URL. I did follow the steps to hook up to Google, but I feel like I must be missing something.

@satterly
Copy link
Contributor

satterly commented Dec 9, 2014

The domain guardian.co.uk should not be hard-coded in the Google OAuth library at https://github.com/guardian/elk-stack/blob/master/src/lib/google-oauth.js#L72
To fix this change guardian.co.uk to the domain of your Google email address (most likely gmail.com).

This should really be a configuration option that an end-user can set in config/config.js. I'm on it.

@satterly satterly added the bug label Dec 9, 2014
@jessepmsi
Copy link
Author

Makes sense. Ill give that a shot.

Great scripts though, saved me a ton of time getting this setup. I like having it all on one box that scales rather than multiple levels - saves money if you have a small deployment.

@satterly
Copy link
Contributor

satterly commented Dec 9, 2014

Be aware that changing the domain to gmail.com means that anyone with a Google email address could log into your Kibana. I'd strongly suggest using security groups to ensure that access is restricted to an authorised IP range.

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

No branches or pull requests

2 participants