Re: Getting 401 With secure websockets on AWS

2017-06-29 Thread Knapp, Michael
headers. Michael Knapp From: "Knapp, Michael" <michael.kn...@capitalone.com> Reply-To: "users@zeppelin.apache.org" <users@zeppelin.apache.org> Date: Tuesday, June 27, 2017 at 3:25 PM To: "users@zeppelin.apache.org" <users@zeppelin.apache.org> Subjec

Re: Getting 401 With secure websockets on AWS

2017-06-27 Thread Knapp, Michael
directly on an ec2. From: Khalid Huseynov <kha...@apache.org> Reply-To: "users@zeppelin.apache.org" <users@zeppelin.apache.org> Date: Thursday, May 4, 2017 at 4:30 AM To: "users@zeppelin.apache.org" <users@zeppelin.apache.org> Subject: Re: Getting 401 Wit

Re: Getting 401 With secure websockets on AWS

2017-05-04 Thread Khalid Huseynov
Hi Michael, Which version of Zeppelin are you using? On Sat, Apr 22, 2017 at 3:10 AM, Knapp, Michael < michael.kn...@capitalone.com> wrote: > Hi, > > > > I am getting a 401, unauthorized, with all secure (and non-secure) > websocket calls while running on AWS. I have configured the server >

Getting 401 With secure websockets on AWS

2017-04-21 Thread Knapp, Michael
Hi, I am getting a 401, unauthorized, with all secure (and non-secure) websocket calls while running on AWS. I have configured the server properly to use a signed certificate, I have tested and all HTTPS calls are successful. I also have LDAP working. Still, the websocket calls are all