-
Notifications
You must be signed in to change notification settings - Fork 311
Need a way to uniquely identify an application. #70
Comments
@Eilon .. can we prioritize this for beta? |
Need to talk to @GrabYourPitchforks about what the design should be for anti-forgery tokens. It's not clear to me that this feature is needed (or that even if it exists, that it will do what is needed for anti-forgery tokens). |
Sorry for not including the details in the bug earlier: |
@yishaigalatzer @Eilon will we be taking this for Beta3? |
@muratg - this is in his realm now. |
@muratg any updates ... dont think we are getting this done for beta3? |
@harshgMSFT we need to be closing on beta3 very soon there'a a couple higher pri items for @GrabYourPitchforks. Also not sure if we should rush the design. @GrabYourPitchforks what do you think? |
@muratg ping. We need to converge on this. Lets meet this week and figure out our options. |
Adding this to the agenda for next mondays core design meeting, unless you discuss it before then. |
@glennc did we get any headway on this ? |
@harshgMSFT Looks like #177 is describing a way to do this in a specific way, and is assigned to you. Is this one OK to close? |
Sure..lets keep the details in both bugs though. |
@harshgMSFT See this bug filed by @GrabYourPitchforks: https://github.com/aspnet/Helios/issues/113 |
Discussed offline with some people. We think the best course of action right now would be to expose this in DataProtection (since only it and MVC require it, and MVC depends on DataProtection) for now. If we can find a legitimate scenario for moving this lower in the dependency chain into DNX or Hosting, then we can do that in a future release. The new API in DataProtection.Interfaces is here. @harshgMSFT - feel free to resolve as appropriate. |
@harshgMSFT Can we close this now? |
Closing as we decided to use data protections api. |
This is needed for
aspnet/Mvc#584
The text was updated successfully, but these errors were encountered: