Thanks. I fixed the permissions. Everyone should be able to comment.
Mike
On Thu, Nov 14, 2024 at 10:42 PM Jean-Baptiste Onofré
wrote:
> Hi Michael
>
> Thanks for sharing the doc.
> Can you please give everyone the permission to comment on the doc ?
>
> As discussed, to implement muti-authentic
Hi Michael
Thanks for sharing the doc.
Can you please give everyone the permission to comment on the doc ?
As discussed, to implement muti-authenticators and SSO, I think we
have to decouple in two parts:
- the core Polaris model and design
- the impl depending of the runtime framework (dropwizar
Hey folks
As discussed during the community sync, I've put together some thoughts on
how we'd add support for federated identities in Polaris. I copied over
some of what I had in the issue at
https://github.com/apache/polaris/issues/441 and put it into the doc here:
https://docs.google.com/docume
Hi folks,
Thanks everyone for joining the Polaris Community Sync.
Here's the record:
https://drive.google.com/file/d/1a2B5c0hychdRuIcNSl2ltEkoH3VcR0J1/view?usp=sharing
NB: I updated the invite to have the meeting at 9am PST now.
Thanks,
Regards
JB
> Although, I wonder if this custom
context isn't identical to the standard request context? IOW, is it
possible for the Polaris context to change during an HTTP call to Polaris
API? I don't think so, which leads me to think that, at least in Quarkus,
we'd use the standard @RequestScoped annotation
Hi
Using @Named is fine with Quarkus. We can also create custom qualifier
(with Literal): named is actually a qualifier :)
I think we discussed about the plan, and to my understanding:
1. I open the Quarkus PR (as draft) to keep what we did
2. We improve the current structure:
2.1. polaris-core
