Skip to content
This repository has been archived by the owner on Dec 14, 2017. It is now read-only.

Unable to expose offered claims through metadata #39

Open
bgregorius opened this issue Apr 21, 2015 · 7 comments
Open

Unable to expose offered claims through metadata #39

bgregorius opened this issue Apr 21, 2015 · 7 comments

Comments

@bgregorius
Copy link

Looking back in the IdentityServer2 code there used to be a way to expose the offered claims in the wsfed/metadata document. This was done through implementing a custom ClaimsRepository and overriding GetSupportedClaimTypes()

This customization of the metadata document no longer seems possible in IdentityServer3. Are there plans to add this back in? If not I'll have to port the project I am working back to IdentityServer2 and that seems like a step in the wrong direction.

@leastprivilege
Copy link
Member

We don't have it right now - and it is not planned so far.

This feature is/was rarely used in v2 or other STS products like ADFS. What's your use case?

@bgregorius
Copy link
Author

Our use case in our product is that we pull the metadata then dynamically generate a UI for mapping the claims from the IdP (in this case IdentityServer3) to our system (acting as the SP).

@leastprivilege
Copy link
Member

OK - I see the issue. We don't have that right now.

I'll add it to the todo list.

@brockallen
Copy link
Member

Are you still interested in this? If so, you can propose a PR. If not, then we will close this.

@bgregorius
Copy link
Author

We are still interested in this enhancement.

I have locally hacked some changes in that just add the specific claims in the metadata that I need for my implementation. It would be nice to see these be able to be configured in though.

@brockallen
Copy link
Member

In all reality, this won't get in unless you can submit a PR. We're swamped with other features/work. Thx.

@scottbrady91
Copy link
Member

@bgregorius If you want to pass across your changes for this, I'd be happy to clean it up and create a pull request.

@leastprivilege leastprivilege removed their assignment Oct 27, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants