Migration 0.8 -> 0.9 / @Auth doesn't have required attribute any more

Dropwizard 0.8 had an attribute to @Auth so you could annotate a method with

@Auth(required = false)

Dropwizard 0.9 doesn’t. The Migration Guide doesn’t describe how to solve this. I found a discussion #1162 about @PermitAll but I am not sure if I read it correctly and if this discussion is up to date with the release of 0.9.

Please write a short paragraph in the migration guide on how to handle this.

Thanks!

[R-Gerard]

+1 for missing the required = false flag.

According to the 0.9 documentation:

If you have a resource which is optionally protected (e.g., you want to display a logged-in user’s name but not require login), you need to implement a custom filter which injects a security context containing the principal if it exists, without performing authentication.

I’d rather not implement a new filter just because one of my APIs has optional auth. I looked into extending OAuthCredentialAuthFilter, but its constructor is private (so the class is essentially marked final), which forces me to copy-paste the implementation. 😞

@ahus1 's solution works for me. Perhaps this should be included in the documentation as an alternative to rolling your own auth filter.

[github-actions[bot]]

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 14 days