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

AuthorizeAttribute(IEnumerable<Claim>) doesn't make sense #9

Closed
victorhurdugaci opened this issue Apr 29, 2014 · 3 comments
Closed

AuthorizeAttribute(IEnumerable<Claim>) doesn't make sense #9

victorhurdugaci opened this issue Apr 29, 2014 · 3 comments

Comments

@victorhurdugaci
Copy link
Contributor

The constructor overload for AuthorizeAttribute taking an IEnumerable as argument doesn't make sense because .NET expects all attribute arguments to be compile time constants.

cc @sebastienros
@victorhurdugaci victorhurdugaci changed the title AuthorizeAttribute(IEnumerable<Claim> claims) doesn't make sense AuthorizeAttribute(IEnumerable<Claim>) doesn't make sense Apr 29, 2014
@sebastienros
Copy link
Member

We should move this issue to WebFX. I agree we need an overload with a single claim, but multiple ones do make sense in the sense they represent a logical OR.

@Praburaj
Copy link
Contributor

Moving this bug to MVC as it belongs to MVC.

@Praburaj Praburaj mentioned this issue Dec 23, 2014
Closed
@Praburaj
Copy link
Contributor

This issue was moved to aspnet/Mvc#1740

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@sebastienros @Praburaj @victorhurdugaci