I'm trying to migrate for Spree Commerce to Magento 1.8 and I have a problem with user passwords. Can I get any NFO from you guys how I can achieve this goal. How passwords are encrypted (bCrypt, MD5 etc.)? Is it possible to decrypt it with PHP and save it while migrating Spree user data to Magento.
Regards,
The most popular user management extension for Spree is spree_auth_devise, which is build on the popular Devise project. By default, Devise uses bcrypt to digest passwords. It is not possibly to decrypt a digested password.
If you with to maintain user accounts during your migration, you will have to modify Magento to use the same algorithm that devise uses to verify passwords.
For more information you should look at the Devise source:
https://github.com/plataformatec/devise/blob/master/lib/devise/models/database_authenticatable.rb
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 social login based application using Django on the backend and I want to know whether it is a good practice to do Social Auth(facebook, google, github, twitter etc.) on the front end or the backend of an application?
For example, If I want to allow a user to signup using their facebook account, is it a good idea to handle that using JavaScript on the front end or using Django on the backend(e.g, using something like social_auth_app_django)?
Both sides =) The authToken you store should placed in your backend while the session interaction could be done with the frontend.
If you are a beginner ,My recommendation is to go with Django Social Auth.
Django Social Auth is an easy way to setup social authentication/authorization mechanism for Django projects.
docs : http://django-social-auth.readthedocs.io
github :https://github.com/omab/django-social-auth
Installation:
pip install django-social-auth
I need to create an application with Laravel authentication system that matches password from a Django database, Django uses PBKDF2 to hash a password. (Django encryption info here)
You will need to write it. Blowfish is considered more secure though, just for your understanding.
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.
I am porting my website from raw php to Django. I have used inspectdb to create models for the existing database. The problem that has come is that earlier I was registering the users and saving their passwords as a md5 hash md5($pass) and Django does not support this md5 version.
Is there a way I can support my legacy database of user and for new users make use of the powerful Django user model that supports user profile?
See the documentation on authentication backends and writing an authentication backend.