Hello,
Sorry, we actually thought about it before doing it (see
https://groups.google.com/d/msg/pac4j-dev/Pv6Rk-F2RJ4/bZJxaWReBwAJ) and
concluded that there shouldn't be any problem since it was opensource, made
by the community for the community, and completely of interest to users of
Jersey (and other frameworks).
We were wrong :)
Sorry again, it won't happen again, and I will take that into account also
for other mailing lists!
So, now, you are not interested by future informations about pac4j's
integration with Jersey (for major changes, no minor ones)?
Thanks for contacting me about this!
Victor
2016-11-18 10:24 GMT+01:00 Pavel Bucek <pavel.bucek_at_oracle.com>:
> Hi Victor.
>
> Please don't send any product/project announcements to Jersey (and I'm
> sure this applies to other mailing lists as well) mailing list without
> asking for permission from project owners.
>
> Regards,
> Pavel
>
>
>
> On 18/11/2016 10:10, Victor Noel wrote:
>
>> Hi,
>>
>> The pac4j team (http://www.pac4j.org/) is happy to announce the release
>> of the first version of jax-rs-pac4j (Apache 2.0).
>>
>> Pac4j is a Java security engine to protect web applications, it is
>> integrated with many frameworks and now with JAX-RS runtimes. It supports
>> most authentication mechanisms, such as OAuth (Facebook, Twitter,
>> Google...), SAML, CAS, LDAP, SQL, JWT, MongoDB, and others.
>>
>> jax-rs-pac4j provides ways to protect your resources using annotations or
>> global filters to protect your application. It has been tested with Jersey
>> and Resteasy, both with servlet and non-servlet containers.
>>
>> It also supports injection at resources method level of the authenticated
>> profile in Jersey.
>>
>> You can find more details at https://github.com/pac4j/jax-rs-pac4j.
>> The maven artefacts are released on Maven central.
>>
>> Note also that for users of dropwizard, we released an integration of
>> pac4j that relies on jax-rs-pac4j and add configuration support (see
>> https://github.com/pac4j/dropwizard-pac4j).
>>
>> We hope the community we use it, we are very open to contributions and
>> issue reports to improve it (it is still young but used in some real
>> projects :).
>>
>> Cheers,
>>
>> Victor
>>
>
>