Hi,
Thanks for posting this!
One thing that can be improved here; slide 25 and 28 are still using the
term "authenticator" (should be authentication mechanism).
The current proposal doesn't use an annotation for user provided ones, but
rather the "one and only class implementing the simplified interface" and a
typed annotation (no class argument) for build-in authentication mechanism
(so the implementation can be vendor specific).
Of course all of that is still in proposed state, but (correct me if I'm
wrong) I think that is closer to the final API than the annotation with
class name attribute.
Anyway, thanks again for posting this and for speaking about it ;)
Kind regards,
Arjan Tijms
On Sun, Jan 3, 2016 at 4:52 PM, Werner Keil <werner.keil_at_gmail.com> wrote:
> Dear Experts,
>
> Here's a picture from my JSR 375 session in Tel Aviv before Christmas:
>
> https://www.facebook.com/codemotiontlv/photos/pb.564453833677998.-2207520000.1451834982./792488317541214/?type=3&theater
>
> I also just uploaded the slides to SlideShare:
>
> http://www.slideshare.net/keilw/jsr-375-have-you-seen-java-ee-security-api-lately-codemotion-tel-aviv-2015
>
> Kind Regards,
> Werner
>