can't start prestodb server over https with a custom password authenticator
See original GitHub issueHi, I’m using presto 0.206 and trying to config it to run over https with a password authenticator that i wrote.
I get the following error -
2018-10-29T16:24:45.974+0200 INFO main com.facebook.presto.server.security.PasswordAuthenticatorManager -- Loading password authenticator --
2018-10-29T16:24:45.976+0200 INFO main Bootstrap PROPERTY DEFAULT RUNTIME DESCRIPTION
2018-10-29T16:24:45.980+0200 INFO main com.facebook.presto.server.security.PasswordAuthenticatorManager -- Loaded password authenticator v3io --
2018-10-29T16:24:45.989+0200 INFO main com.facebook.presto.server.PrestoServer ======== SERVER STARTED ========
2018-10-29T16:24:45.989+0200 ERROR Announcer-0 io.airlift.discovery.client.Announcer Cannot connect to discovery server for announce: Announcement failed for https://192.168.224.157:8889
2018-10-29T16:24:45.990+0200 ERROR Announcer-0 io.airlift.discovery.client.Announcer Service announcement failed after 9.44ms. Next request will happen within 0.00s
looks like my plugin ("v3io") is loaded successfully but something is wrong with the https config
config.properties -
coordinator=true node-scheduler.include-coordinator=true http-server.https.port=8889 query.max-memory=5GB query.max-memory-per-node=1GB discovery-server.enabled=true discovery.uri=https://192.168.224.157:8889 node.internal-address=192.168.224.157 http-server.https.keystore.path=/opt/presto-server-0.206/keystore.jks http-server.https.keystore.key=password http-server.authentication.type=PASSWORD
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (2 by maintainers)
Top Results From Across the Web
can't start prestodb server over https with a custom password ...
Change the discovery.uri value to be http not https . I don't think it supports HTTPS.
Read more >LDAP Authentication — Presto 0.278 Documentation
Presto can be configured to enable frontend LDAP authentication over HTTPS for clients, such as the Presto CLI, or the JDBC and ODBC...
Read more >Simplifying User Access in Presto with File-Based Authentication
Presto Server will now be accessible over HTTPS and on port 8443. Username and passwords are mandatory. For example, the JDBC URL to...
Read more >Presto Custom Password Authentication Plugin (Internal)
Anyway, your plugin won't work because password plugins don't do anything unless you have HTTPS enabled on the coordinator. This is because ...
Read more >Using LDAP authentication for Presto on Amazon EMR
If anonymous binding is disabled on PrestoDB, you need the user ID (UID) and password of an account with permissions to bind to...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
that works! thanks! my confusion was that i thought discovery.uri should be the same as the config passed to --server in cli
Hi I am also working with username and password. after authentication while querying presto db with “show catalogs;” I am getting below error “Error running command: java.net.ConnectException: Failed to connect to /127.0.0.1:8443”. can anyone help me with the rot cause and solution