[
https://issues.apache.org/jira/browse/IMPALA-10496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17287469#comment-17287469
]
ASF subversion and git services commented on IMPALA-10496:
----------------------------------------------------------
Commit 9c990dedacf85f51cdff99195147e01b413b729e in impala's branch
refs/heads/master from Csaba Ringhofer
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=9c990de ]
IMPALA-10496: Remove checking port in FLAGS_saml2_sp_callback_url
Enforcing that the port in FLAGS_saml2_sp_callback_url must be the same
as hs2_http_port causes problems if the port is mapped, e.g. in
containerized setting.
Change-Id: I2534b7a1a2bf16bf48ba533dc13fd300f690f4e5
Reviewed-on: http://gerrit.cloudera.org:8080/17087
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> Support SAML authentication in Impyla
> -------------------------------------
>
> Key: IMPALA-10496
> URL: https://issues.apache.org/jira/browse/IMPALA-10496
> Project: IMPALA
> Issue Type: Improvement
> Components: Clients
> Reporter: Csaba Ringhofer
> Priority: Major
> Labels: impyla
>
> IMPALA-10437 adds SAML2 browser profile support to Impala.
> Supporting it in Impyla would allow implementing SAML auth for Impala shell,
> and make SAML related EE tests simpler.
> The simplest way would be to allow passing a bearer token in
> https://github.com/cloudera/impyla/blob/0914895830609001b9d4f535573cba8db487d45e/impala/hiveserver2.py#L796
> I am not sure about the other parts of the SAML logic (e.g. communication
> with the browser) - it could be added to Impyla too or reside in Impala shell.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
