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 }}
This repository has been archived by the owner on Sep 18, 2021. It is now read-only.
I've been playing around with using a custom ExternalClaimsFilter and Windows Azure AD. I would like to filter claims differently when the provider being used is WAAD, but the only property to identify the current identity provider is the Name property. For Twitter and Facebook this comes across as the string "Facebook" or "Twitter".
It looks like the name property gets set in ExternalIdentity.cs to always equal the Issuer of the NameIdentifier claim type. In the case of WAAD, that value is a rather ugly URL with a guid identifier. Is there any way to add the ability to customize the Name property of the identity provider when you wire it up in the Startup.cs class?
Either way, great job on version 3! It seems to be much more flexible/customizable than the previous version.
The text was updated successfully, but these errors were encountered:
So right now we only support the katana social identity providers and yes, the provider name passed to the filter is the name as registered with katana. We will eventually support other idps (#59) and whatever identifier we use for those will be passed.
Hello,
I've been playing around with using a custom ExternalClaimsFilter and Windows Azure AD. I would like to filter claims differently when the provider being used is WAAD, but the only property to identify the current identity provider is the Name property. For Twitter and Facebook this comes across as the string "Facebook" or "Twitter".
It looks like the name property gets set in ExternalIdentity.cs to always equal the Issuer of the NameIdentifier claim type. In the case of WAAD, that value is a rather ugly URL with a guid identifier. Is there any way to add the ability to customize the Name property of the identity provider when you wire it up in the Startup.cs class?
Either way, great job on version 3! It seems to be much more flexible/customizable than the previous version.
The text was updated successfully, but these errors were encountered: