You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
or another alternative we could have the following annotation based (maybe this is the best way?)
.authorizeRequests()
.annotationBased() // scan classpath
...
.denyAll() // deny by default, anything not configured by a annotation is not allowed or maybe allow authenticated or other such by default here...
... cors()...etc
public interface UserRepository extends PagingAndSortingRepository<User, Long> {
@HttpSecurity( method = HttpMethod.POST, permitAll = true )
@Override
... save(...);
}
or maybe there's a better idea/api for ensure that if I update some parent route all of the security doesn't need to be reaudited. also prepending /v0/.mvcMatchers( HttpMethod.POST, "/v0/users" ).permitAll() seems like it might get a bit tedious.
The text was updated successfully, but these errors were encountered:
xenoterracide
changed the title
some reflection based method of supply HttpSecurity
Suggestion: some reflection based method of supplying HttpSecurity
Aug 23, 2016
Feature Request
So I have this,
and it works fine... well actually I broke it when I set this, which is sort of the crux of my problem, I changed a path and it broke my security.
but I think it would be cool if we could define security like this
or if I had an mvc controller
maybe
or another alternative we could have the following annotation based (maybe this is the best way?)
and controller example
or maybe there's a better idea/api for ensure that if I update some parent route all of the security doesn't need to be reaudited. also prepending
/v0/
.mvcMatchers( HttpMethod.POST, "/v0/users" ).permitAll()
seems like it might get a bit tedious.The text was updated successfully, but these errors were encountered: