StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
2289973
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2010-02-18T15:56:56.747
FavoriteCount
0
LastActivityDate
2010-02-18T15:56:56.747
LastEditDate
2017-05-23T12:03:01.573
LastEditorUserId
-1
OwnerUserId
208871
ParentId
2279621
PostTypeId
2
Score
4
ViewCount
0
LastEditorDisplayName
text
Body
I will leave how to inject your own custom authentication provider to the other myriad of examples from <a href="http://www.google.com/search?q=spring+security+custom+authentication+provider&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-US:official&client=firefox-a" rel="nofollow noreferrer">Googleland</a> and here on <a href="https://stackoverflow.com/questions/448204/creating-a-custom-authentication-with-acegi-spring-security">StackOverflow</a>. It looks like it has to do with marking a particular bean with the xml. But hopefully I can fill in some of the other details for you. So you've defined the class somewhat like above and I'll add more of the details that you'll need for Spring (i.e. merge the stuff from above as well. <pre><code>public class SwitchingAuthenticationProvider implements AuthenticationProvider { .... public List<AuthenticationProvider> getProviders() { return delegateList; } public void setProviders(List<AuthenticationProvider> providers) { this.delegateList = providers; } .... } </code></pre> This will allow you to inject a host of providers using spring: <pre><code><bean id="customAuthProvider1" class=".....CustomProvider1"> ... </bean> <bean id="customAuthProvider2" class=".....CustomProvider2"> ... </bean> ... <bean id="customAuthProviderX" class=".....CustomProviderX"> ... </bean> <bean id="authenticationProvider" class="....SwitchingAuthenticationProvider"> <security:custom-authentication-provider/>  <property name="providers"> <list> <ref local="customAuthProvider1"/>  <ref local="customAuthProvider2"/>  ... <ref local="customAuthProviderX"/>  </list> </property> </bean> </code></pre> In the end how you populate the providers could be any means of getting the delegator a collection of providers. How they map up to which one to use is up to you. The collection could be a named mapped, based on the current state of the delegator. It could be a list of more than one to try. It could be two properties, "get/setPrimary" and "get/setSecondary" for fail-over like functionality. Once you have the delegator injected the possibilities are up to you. Let me know if this isn't answering your question.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POSwitching authentication approaches at runtime with Spring Security?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCommunity
UserOwnerUserId
1. USMatt
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POSwitching authentication approaches at runtime with Spring Security?
 singulars
 PostTypePostTypeId
 PTQuestion
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
 VTAcceptedByOriginator
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. CO@Matt Thank you. This helps. I will try this out and let you know.
 singulars
 PostPostId
 PO
 UserUserId
 USJay

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.