Sunday, January 24, 2016

Re: The best approach for a customer restricted area


On Jan 22, 2016 11:39 AM, "Miguel Pragier" <miguelpragier@gmail.com> wrote:
>
> Hi all.
>
> I was demanded to create an online service/portal in Django, and this is my first project in Django.
>
> Roughly, the portal should have two restricted areas:
> - Our ( operators/providers ) restricted area, supposed to be created with "admin" generator.
> - Our customer's restricted area, with ther own authentication system.
>
> How should I create this "customer area"?
> Admin?
> Some plugin/add-on?
> Coding from scratch?
>
> Or am I looking to the wrong direction?
>
> Thank you very much.
>

If the customer has a separate authentication system, then your strategy would be driven by whatever system they are using. There are various libraries that can help, such as django-ldap if they are using an LDAP server for authentication.

You'll need to write separate views that handle logins using the alternate form of authentication, or have a single login page that can use multiple authentication systems if you want everyone to log on through the same page. Both are entirely possible.

Access to pages and resources can be controlled by the built-in Django auth system in most cases, using permissions and groups.

-James

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CA%2Be%2BciVEfje%3DkoksvtKo-Hvgtk9GNQC6VC_323resGesMuFVcg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

No comments:

Post a Comment