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
{{ message }}
Repository navigation
Spring Boot Adapter - security constraint vs policy enforcer
#14828
I'm using the Keycloak Spring Boot adapter as described here and trying to understand the difference between specifying security constraints and a policy enforcer configuration.
Step (2) in the above document states that a policy enforcer can be specified. Step (3) describes setting up Java EE security config using security constraints. These two steps appear to provide very similar functionality so I am not sure if both or one of these steps needs to be set.
Could some explain the differences between these two steps and if it is a choice of using one or the other and where each method is more appropriate to use?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
I'm using the Keycloak Spring Boot adapter as described here and trying to understand the difference between specifying security constraints and a policy enforcer configuration.
Step (2) in the above document states that a policy enforcer can be specified. Step (3) describes setting up Java EE security config using security constraints. These two steps appear to provide very similar functionality so I am not sure if both or one of these steps needs to be set.
Could some explain the differences between these two steps and if it is a choice of using one or the other and where each method is more appropriate to use?
All reactions