Skip to content
This repository has been archived by the owner on Jul 31, 2024. It is now read-only.

Assert Required Claims Flexibility #820

Closed
Lutando opened this issue Feb 15, 2017 · 3 comments
Closed

Assert Required Claims Flexibility #820

Lutando opened this issue Feb 15, 2017 · 3 comments
Labels

Comments

@Lutando
Copy link
Contributor

Lutando commented Feb 15, 2017

Some context of my issue over here. The short of it, is that it seems I cannot SignIn() a user if the principal does not contain the name claim even if the principal has been specified to use a different claim type as the name claim.

In my case I would like to use the "preferred_username" as the principals name. I am pretty sure that the claims principal has the claim type of where the name came from as well, so this wouldn't be too much of a fuss to do. Could something like checking for the name claim type rather than just doing a blanket check on the claim type "name" like it is now? The LOC in question is here

Thanks.

@leastprivilege
Copy link
Member

We simply use a claim called name for the UI. Simply create a name claim with whatever content you want.

@Lutando
Copy link
Contributor Author

Lutando commented Feb 15, 2017

OK. I guess all is good then. Thanks a lot.

@Lutando Lutando closed this as completed Feb 15, 2017
@lock
Copy link

lock bot commented Jan 15, 2020

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Jan 15, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants