Handling 'RequireAccountVerification' when federating across multiple IdPs about identityserver3.membershipreboot HOT 6 CLOSED

Well, if they're authenticing from an external IdP, you can always set the user's email as verified (assuming you trust twitter, etc. to have already validated the email). There's an API on the user account service to set the verified email.

from identityserver3.membershipreboot.

Indeed, my issue is however that the 3rd party (twitter in this case) will never provide the e-mail, so I'd like to 'adjust' the semantics of the Membershipreboot library (in this case 'requires verified email') depending on the IDP federated onto. I can see how I could probably achieve this, but wonder if its relevant to the general library?

from identityserver3.membershipreboot.

I'm confused -- if the user authenticates w/ twitter then the MR Authenticate API is not used and that's where the RequreAccountVerification is checked (unless I'm forgetting something).

from identityserver3.membershipreboot.

When the call comes back in from twitter, it still passes through ProcessNewExternalAccountAsync which (if MR is configured so) requires an e-mail address to be present in the claims, I'd like that bit, just there to be tweakable depending on my whims ?

from identityserver3.membershipreboot.

Yea, if this is being enforced by the MR user service, then just tweak that how you like it.

from identityserver3.membershipreboot.

yeah I've spent a chunk of time getting my head around (it's been a while since I've been in the IdSrv internals) registration and I now know how I can get my per-request bits and pieces routed into the relevant place so should be able to do what I need with a facade around it I think :) ty.

from identityserver3.membershipreboot.