asp.net web api - WebApi 2.1 File > New Project > MRB or default MS bits -
Hope this topic is not closed but .....
I create a new brand Wish WebAP 2.1 project and also an MVC 5 site (I will convert it to an angle site on any other day).
My application requires roles and authentication and the ability to send details for the encrypted example to client ID and other things I do not want to see the end user in plain text.
I have all the heavy to take to take place at the API level because I do not want to apply the subscription client level will obviously need the site to log a user, but I API website There was hope to call
This is less than the path of least resistance :)
I subscribe today I see Rebot and it looks promising and looks for pieces created with Microsoft's recent updates is.
I do not think what I want to do, it is very difficult, I just do not want to waste a lot of time going down once again, again I need to start again.
My question is whether I want to select one of these two (If there are open IMs for other suggestions)
- Authentication via API - On returning, I think a carrier token or something similar
- Setting a custom value within the token sent by the server / client client / server
- A multi-tenant Take a look at the subdomain example Site1.mydomain.com site2.mydomain.com
I hope someone cares for me I can say in the same direction and I am happy to trade beer or coffee for some good advice.
Thank you!
I believe that you will need the following capabilities:
- < Li> Token production / management is available in the web APIs for core capabilities, but to get a full-featured product or to get a commercial product.
- Authorization management for Web APIs Apply a custom authorization feature or get the Identity Model Library at the Thinktecture link above.
- Membership / Role Structure One option is to extend the new identity model provided with ASP.NET MVC5. It's a good observation of how to do this
Comments
Post a Comment