如何在 ASP.NET MVC 应用程序中附加自定义成员资格提供程序?
如何将自定义成员资格提供程序与 ASP.NET MVC [Authorize()] 属性绑定在一起?我已经浏览了许多有关如何创建自定义成员资格提供程序的教程,但我发现的有关如何将其连接到应用程序的所有信息似乎都围绕常规 ASP.NET WebForms 应用程序,这似乎是一个整体蛋糕。
我对 ASP.NET MVC 中发生的大量“魔法”感到困惑,这很棒,但我习惯于以 WebForms 方式插入内容,因此这种“它只是有效”的方法有点过分对我来说是令人费解的。我怎么知道什么时候我应该承担繁重的工作,或者我应该依靠它的神奇发生?
我在哪里将我的提供商与 MVC 应用程序绑定?我是否正确地假设一旦我将其连接起来就通过 [Authorize()] 属性调用它?
How do I tie up my custom membership provider with my ASP.NET MVC [Authorize()] attribute? I've blasted through a number of tutorials for how to create a custom membership provider but all the information I've found about how to hook it up to an application seems to revolve around regular ASP.NET WebForms applications which seem to be a piece of cake.
I'm coming unstuck with the amount of "magic" that just happens in ASP.NET MVC which is great, but I'm used to plugging stuff in in a WebForms way so this "it just works" methodology is a bit of a mind bender for me. How do I know when I'm supposed to do the heavy lifting or I'm supposed to just rely on it happening by magic?
Where do I tie my provider in to an MVC app? Am I right in assuming that it is invoked through the [Authorize()] attribute once I do get it hooked up?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(3)
希望我可以对其他答案进行一些额外的澄清,因为它们确实没有解释正在发生的事情,这不会帮助您解决困惑。
首先,根据您已经完成的事情实现您的自定义提供程序,因此我将仅提供一些代码片段,并且不会在此处详细介绍任何进一步的细节:
然后您在 Web 中配置您的提供程序。确保填充配置基本 MembershipProvider 的属性:
下一步我认为您想太多了,与您的 Web 应用程序的实际搭配。而在 WebForms 应用程序中,您必须自己编写其余的代码 - MVC 框架会为您完成其余的工作 - 您所需要做的就是将 [Authorize] 属性添加到您的操作方法中,框架将检查您是否已登录,如果未登录,则将您重定向到登录页面。 因为这是在 web.config 中配置的内容,并将让您的用户登录。您可以通过引用 User 对象从控制器访问有关登录用户的信息:
登录页面将找到您的自定义提供程序, 此操作要求用户登录并将用户信息提供给Whatever/WhateverAction.aspx 视图以显示在页面上。
Hopefully I can add some additional clarity over the other answers as they really don't explain what's going on which isn't going to help your confusion.
First up, implement your custom provider which from the sound of things you've done already, so I'll just throw up a little code snippet and won't go into any further detail here:
Then you configure your provider in your web.config making sure to populate the attributes that configure the base MembershipProvider:
The next bit I think you're overthinking, the actual tie-in to your web application. Whereas in a WebForms app you kind of have to code the rest for yourself - the MVC framework does the rest for you - all you need to do is add the [Authorize] attribute to your action method and the framework will check to see if you're logged in, and if not redirect you to the login page. The login page will find your custom provider because that's what's configured in the web.config and will log your user in. You can access information about the logged in user from your controllers by referencing the User object:
So this action requires that the user is logged in and presents the user information to the Whatever/WhateverAction.aspx view to be displayed on the page.
我的自定义会员资格提供程序在 web.config 中引用:
然后只需使用静态会员资格类。
My custom membership provider is referenced in the web.config:
Then just use static Membership class.
您对这个自定义会员资格做了多少改变?比如你改变了表名吗?你可以让用户登录吗?即您的自定义会员资格有效吗?
如果您更改了很多内容,例如将角色表名称更改为不同的名称或类似的内容,那么您将必须覆盖 Authroize 标签。
但是,如果您的自定义会员资格不起作用,那么您可能没有正确配置它,并且配置与 Web 表单中的配置相同。你只需要设置你的网络配置。
How much did you change in this custom membership? Like did you change table names around? Can you log users in and stuff? Ie is your custom membership working?
If you changed lots of stuff around like you changed the roles table name to something different or stuff like that then your going to have to override the Authroize tag.
However if your custom membership is not working then you probably have not configured it right and configuring is the same as in webforms. You just have to setup your webconfig.