[
https://issues.apache.org/jira/browse/PHOENIX-6750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17581875#comment-17581875
]
ASF GitHub Bot commented on PHOENIX-6750:
-----------------------------------------
joshelser commented on PR #104:
URL:
https://github.com/apache/phoenix-queryserver/pull/104#issuecomment-1220723802
> I see Set-Cookie: JSESSIONID... lines in the log and the cookies being
used.
Awesome, that sounds right.
> could you give us a little explanation why was the realm trimmed off in
calcite?
Sorry, I missed this question yesterday :)
Calcite isn't pulling it off, but it's actually being done by Jetty. There
was a pretty fundamental change in the spnego code that we _used_ to use in
Avatica/Phoenix (now, deprecated in Jetty) and the spnego code that Avatica is
now using. I'm going off of memory here... but it was something like the old
version of Jetty would let you define "realms" that were allowed to talk to
that Jetty server. So you could say "SALES.COM" and "FINANCE.COM" could talk to
the service but not "HR.COM".
The newer version of the spnego impl did away with that logic. If you have a
valid krb auth'n, then you're good to go.
> Bump Avatica version to 1.21.0 in queryserver
> ---------------------------------------------
>
> Key: PHOENIX-6750
> URL: https://issues.apache.org/jira/browse/PHOENIX-6750
> Project: Phoenix
> Issue Type: Improvement
> Components: queryserver
> Affects Versions: queryserver-6.0.0
> Reporter: Richárd Antal
> Assignee: Richárd Antal
> Priority: Major
>
> Avatica 1.21 has been released.
> It has several fixes that we want.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)