StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
8327582
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-11-30T14:36:52.257
FavoriteCount
0
LastActivityDate
2012-01-13T19:14:31.590
LastEditDate
2012-01-13T19:14:31.590
LastEditorUserId
618087
OwnerUserId
618087
ParentId
8326587
PostTypeId
2
Score
21
ViewCount
0
LastEditorDisplayName
text
Body
The best way to determine the target url based upon roles is to specify a target url in your Spring Security configuration as shown below. This will work in Spring 3.0 or 3.1 <pre><code><http> ... <form-login login-page="/login" default-target-url="/default"/> </http> </code></pre> Then create a controller that processes the default-target-url. The controller should redirect or forward based upon rolls. Below is an example of using Spring MVC, but any type of controller will work (i.e. Struts, a Servlet, etc). <pre><code>@Controller public class DefaultController { @RequestMapping("/default") public String defaultAfterLogin(HttpServletRequest request) { if (request.isUserInRole("ROLE_ADMIN")) { return "redirect:/users/sessions"; } return "redirect:/messages/inbox"; } } </code></pre> The advantages to this approach are it is not coupled to any specific implementation of Security, it is not coupled to any specific MVC implementation, and it works easily with Spring Security namespace configuration. A full example can be found in the <a href="https://github.com/rwinch/spring-security-samples-securemail" rel="noreferrer">SecureMail</a> project I presented at SpringOne this year. An alternative is that you could create a custom <a href="http://static.springsource.org/spring-security/site/docs/3.1.x/reference/ns-config.html#ns-form-target" rel="noreferrer">AuthenticationSuccessHandler</a>. The implementation might extend SavedRequestAwareAuthenticationSuccessHandler which is the default AuthenticationSuccessHandler. it could then be wired using the namespace as shown below. <pre><code><sec:http> <sec:form-login authentication-success-handler-ref="authSuccessHandler"/> </sec:http> <bean:bean class="example.MyCustomAuthenticationSuccessHandler"/> </code></pre> I would not recommend doing this as it is tied to Spring Security API's and it is better to avoid that when possible.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POdetermine target url based on roles in spring security 3.1
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USRob Winch
UserOwnerUserId
1. USRob Winch
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.