Member since
08-24-2018
16
Posts
1
Kudos Received
1
Solution
My Accepted Solutions
Title | Views | Posted |
---|---|---|
1533 | 01-02-2019 04:56 PM |
03-17-2019
04:18 AM
I submitted KNOX-1828 for this issue and have created a pull request for a patch that appears to work.
... View more
01-11-2019
06:06 AM
You were exactly correct, thanks again! For others who might be using an NGINX proxy in front of Knox, the bolded below is what I had to add to me NGINX cfg for the proxy URL: server { listen 443 ssl; server_name PROXIED_URL; ssl on; ssl_protocols TLSv1.1 TLSv1.2; ssl_certificate /etc/ssl/private/CORPORATE_CERT.crt; ssl_certificate_key /etc/ssl/private/CORPORATE_CERT.key; location / { proxy_pass https://KNOX_HOST:8443; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; proxy_read_timeout 86400; }
}
... View more
01-02-2019
04:56 PM
OK, I figured this out...the problem was with the default setting of knoxsso.token.ttl property, which was 30000 (30 seconds). I stopped the Knox service, updated the configuration in Ambari, restarted Knox, and now behavior is correct.
... View more
09-20-2018
03:07 AM
Nevermind, used the PDF docs (https://docs.hortonworks.com/HDPDocuments/HDF3/HDF-3.2.0/installing-hdf/hdf-installing-hdf.pdf) with new VMs and all is good now.
... View more