I'm creating a project using Django.
For this project I use git and redmine.
I'd like to have the same users on my Django project as in redmine.
What do you suggest ?
You could use LDAP for user authentication. django-auth-ldap is an LDAP authentication backend for Django, and Redmine supports LDAP out of the box, so it should be easy peasy.
Related
Using Django Rest framework we can support mobile apps, for websites Django can authenticate users based on social media using Allauth library. When user signup with Facebook ,a new tab opens and authenticate user with permission.
How can we do this for mobile apps ? I think Standard packages like AllAuth wont support it.
I do not need the codes, but any guidance will be useful
Django does't have to do anything with it , the app itself can validate
https://blog.expo.io/google-sign-in-with-react-native-and-expo-9cac6c392f0e
I am building a Django application and I need to connect to an existing external Laravel site to authenticate users. Basically to have two different platforms, but users only have one set of credentials. Also - users should be able to sign up on the Django, and their user is created in the Laravel DB.
The Laravel site has Laravel Passport (OAuth2 based) installed because it uses it for a Flutter app.
I know that REMOTE_USER is "the Django way" of achieving external auth but, I don't know where to go from there. If it makes a difference, the Django app will be a full REST application using DRF because its frontend will be ReactJS.
Can anyone explain how to achieve external auth with Django, particularly when the authentication server is OAuth2 based? Or better yet, how it can work with Laravel Passport in particular.
Thanks
I have a Django installation with userena and django_facebook working pretty fine. Can I somewhat make my authentication work from another database (one database for authentication and another for everything else)? The problem is that the project I'm working on requires the same authentication across different Django installations on servers with one entire server for the databases. Should I make a database router that handles all the apps or is there a better solution?
Authentication backends are what you are looking for. Django documentation: https://docs.djangoproject.com/en/dev/topics/auth/#other-authentication-sources
Simple database routers solved the problem with regular Django authentication and Userena authentication. I'm guessing it will be the same with Facebook as they are chained together. The only downfall is that the user for the admin panel is the same across all sites.
Everyone in our office has a redmine account and so I would like to know if it's possible to use Redmine as an authentication provider.
We create internal websites using django, and rather than having to set up usernames and passwords for each one, for each person, wouldn't it be nicer if I could just click "login using redmine". Just like how on stackoverflow I can click "login with google" which works with OpenID.
Is there any plugin or facility of redmine I can use to achieve this?
Consider Redmine OAuth provider plugin.
https://github.com/suer/redmine_oauth_provider
You could use the Redmine Rest API authentication. It allows you to use user/password to authenticate.
I have a Django web app that I would like to use in a single-sign-on solution for a number of remote apps that use Apache authentication.
I can see how to authenticate Apache from a local Django instance and an old Apache module for doing basic queries off postgresql (but without the syntax support to phrase queries with joins to check Django group permissions)
Any suggestions?
I would like to avoid having to switch to using a directory service in the short term (e.g. ActiveDirectory, LDAP) if possible.
.M.
EDIT: Also found mod_auth_external
The following should work for you.
http://www.openfusion.com.au/labs/mod_auth_tkt/
You can use the apache module to hit a specific view in your Django app to generate a ticket for valid users. Then all the other applications can do basic authentication against Django via a URL.
This gives you SSO using the Django user database for legacy apps using HTTP basic authentication.