I have tried to install Drupal 7.x on AWS by using cloudformation but after the installation, while connecting to the RDS admin the administrator email is not updating.
In the users table,enter image description here I am able to find all the schema that I have given while installing the Drupal site except for mail(Default). The mail field is filled up with "admin#example.com", and I am unable to find my email in the table. Due to this result, am unable to reset my password and also create new users. New users also don't receive emails from the admin.
I am able to see my email in the Drupal site but in the database, I see "admin#example.com" (the default value). What could be going wrong here?
Related
I've just taken a copy of my drupal 8 database from staging and loaded this on my development enviroment.
I now get access denied when I try to login /admin
Can't find any information on why.
Update
Seems to be something to do with a twig service where the urlGenerator is not being implemented. Still no luck fixing this.
In hoster`s panel try find "IP address:" settings and change it from "Dedicated IP" (this option can have dependant "This site processes direct requests to a dedicated IP address" tick) to "Shared IP".
Without doing login in your site, you can not access the admin screen.
For example : If your site is justprogrammer.com and you try to open link justprogrammer.com/admin without login then you are not able to access the page. Before accessing the admin link, you first need to login using justprogrammer.com/user.
You cannot just access any /admin/* pages on drupal without logging in. For that you have to login from /user/login put in the username and relevant password then you can access the admin side if you really have admin role and actually logging in from admin account.
If you don't know the password for admin simply reset them to whatever you want by this drush command.
drush upwd --password="YourPassword" 1
1 is user id of admin.
I was logged as a siteadmin on my local page, after clearing cookies I cannot login again on this same login and password. I tried to upload the backup of the database when i can login, but it not helped, i clear all the cache.
Did someone had a such problem? How to resolve it?
Thanks,
Vergili
try like this:
Go in PhpAdmin and select the database of your drupal website
Scroll down and Go to record users, admin user is always the first user id:1
Make EDIT the first user (admin user) and change field email with your email.
After email changed, go to your website and try to do "forgot password" on your loggin page, you will receive a email restore password in your email inserted in your database.
This can be a way to login again like admin.
If you have Drush installed you can navigate to your sites root directory in the console and type drush uli It will give you a one time login.
it will look like:
http://default/user/reset/1/1464702672/4-mLpgYQqVblYxY3xPq4hY6yF9K1vCvsvfOHgGNyhWg/login
Replace 'default' with your domain.
Informatica Server was setup at our local server, but unfortunately nobody remembers the Admin Console password for user "Administrator".
1.) Using pmpasswd, I created an encrypted password and replaced the current one in PO_USERINFO table "POU_PASSWORD" field, in the database I found on my "Informatica_9.6.0_Services" log file, but the service would not restart. I had to revert it back for the service to run again.
2.) I have tried using default user name/ password combinations but they aren't working
Any suggestion is appreciated.
The only way to reset a lost admin password is at the database level. Informatica Support has a process for this if you contact them.
Do not alter the database yourself!!
Windows 8.1
Ruby 2.0.0
Rails 4.1
Devise 3.xx
In my registrations_controller, I have the following:
#user.skip_confirmation!
prior to saving. This is working only partially, as confirmation email is not being sent out, but the confirmed_at field is being filled, and I can login using the credentials I used to register.
How do I skip confirmation altogether? If there are recommendations on how to confirm later (by an admin), that would be great.
As you don't want them to be able to login until they've later been confirmed by an admin, you can use skip_confirmation_notification! instead of skip_confirmation!. This will create the confirmation token and the user will need to be confirmed, but it won't send the email notification to enable them to confirm themselves. They won't be able to log in until they're confirmed. You can then call user.confirm! for an admin to confirm the user later. This should do the job, but the source code/comments might be worth a browse:
https://github.com/plataformatec/devise/blob/master/lib/devise/models/confirmable.rb
I'm working with:
A) A large Drupal 7.23 application running at https://sitename.com using a MySQL database with thousands of users, around 30 of which are Staff.
B) A small Django 1.3.7 application running at http://dj.sitename.com using a PostgreSQL database with few (only the Drupal app's staff) users, who need to be able to login to this Django app using their existing Drupal credentials.
The workflow would be something like this:
Staff users are manually created with identical usernames in each of the applications.
A staff user goes to dj.sitename.com and inputs the same username and password of their account that was created at sitename.com, and clicks submit. Django checks the username and password against the users table in the Drupal MySQL database and compares it with the details in the Django users table. If they match, the user is logged in.
When a staff user is already logged into the Drupal app and visits the Django app at dj.sitename.com, they are automatically logged in, and vice-versa.
When a staff user logs out from the Django app, they are logged out from Drupal, too, and vice-versa.
When a user changes their password in either Drupal or Django applications, it is automatically changed in both systems.
What is the simplest way to accomplish this?
You can use the Services module to expose Drupal user login as a HTTP service, which can then be used by your custom Django authentication backend. On successful login, the service will return you the Drupal user object. This object include the roles of the user, so you can use it to validate of the user has access to your application.
I had a similar request and I've detailed my solution in this howto. Both Drupal and Django run on the same server so I can use both TCP to share data between the two platforms and drush to do Drupal operations in Django.
Every login/logout has two steps:
Login: Django login -> (auto) Drupal login
Logout: Drupal logout -> (auto) Django logout
The turn point in the analysis of mine was to generate and use the one-time login after the Django login using Drush. Then, I use that generated url as a destination url of a login success in Django and alter or suppressing the password recovery message to avoid one more click.
from subprocess import check_output
output = check_output(["drush", "-r", settings.DRUPAL_SITE_PATH, "-l", settings.DRUPAL_SITE_NAME, "user-login", drupal_id])
Where drupal_id is the drupal uid of the just logged in django user. I have to keep a field for drupal uid in the django database. Via Drush you can even create an user when it's the first time you login successfully.
To logout you have to logout from Drupal and then logout from Django. You can do it via Rules, calling a django logout path after the event User has logged out is triggered.
What you're describing is single sign-on. You can look into phpSimpleSAML and enable SAML on both Drupal and your Django based app. Drupal has a module available here: https://drupal.org/project/simplesamlphp_auth
I'm guessing some type of SAML module/plugin exists for Django already.