-
Notifications
You must be signed in to change notification settings - Fork 865
Conversation
Assert.Equal(claim.Issuer, newClaim.Issuer); | ||
} | ||
|
||
[Fact] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@divega This test depends on the ability to affect querys using the "logincontext" to affect the filter. So this is a scenario which required customizing the LINQ query
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
An alternative way for this scenario to work without exposing all of the querys, would be to extend the user manager and overriding the behavior of the methods to do the right thing, either via new store api or directly applying a query.
@divega This PR has been updated as we discussed, I removed the test that was trying to customize and changing the uniqueness of our login providers, the other 2 tests pass. I also copied the test over to the SqlServer, and those pass as well, so I think this should be good to go. |
Great to see this is now getting traction... thanks for listening |
/// Reads the type and value from the Claim. | ||
/// </summary> | ||
/// <param name="claim"></param> | ||
public virtual void FromClaim(Claim claim) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Initialize
Hand merge with some changes from #643