Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use MachineKey in ASP.NET vNext #240

Closed
daverupp opened this issue Dec 16, 2014 · 7 comments
Closed

Use MachineKey in ASP.NET vNext #240

daverupp opened this issue Dec 16, 2014 · 7 comments

Comments

@daverupp
Copy link

Hey all
I am using a OWIN based IdentityServer and there I have a MachineKey for Token generation. What are the plans to use the MachineKey functionality as well within a ASP.NET vnext MVC 6 Application? There is now way to reference the MachineKey's System.Web dll (Of course that makes totally sense, but what is the alternative?)

My Target:
I want to create access Tokens based on the same key for further usage on the ResourceServer.
(Kind of authorization workflow decoupled from the resource server)

thanks for any help or ideas how to solve that.
Kind regards
Dave

@Eilon
Copy link
Member

Eilon commented Dec 17, 2014

@blowdart
Copy link
Contributor

What creates your tokens?

We'll have a machine key equivalent which should address some of the multi-machine problems, but you may also just want to generate your keys yourself if you're doing the token generation.

(It's not checked in yet though AFAIK)

@GrabYourPitchforks
Copy link
Member

There is already a MachineKey equivalent in vNext; see the https://github.com/aspnet/dataprotection project for more information. Unfortunately we don't really have samples that show how to use it, but I hope to create docs and samples over the next few weeks.

@rjhernandez
Copy link

Did any samples ever get published?

@GrabYourPitchforks
Copy link
Member

@mattlittle16
Copy link

Can DataProtection be used in place of static machine key that one would put into a web.config to sign auth cookies?

@blowdart
Copy link
Contributor

@Red6Porkins Yes, that's what it's designed for, as pointed out above.

The documentation is also pointed to above.

@dotnet dotnet locked and limited conversation to collaborators Feb 16, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants