I am working on a project where we have multiple computers (running chrome) that are used to present webpages automatically.
Some of the webpages displayed on these computers require a login.
Currently we need to remotely login into every computer and enter passwords in order for them to load the pages. However, I would like to be able to login to a site only once and then share the logins throught the different computers.
Is there some way to synchronize sessions across chrome clients, so that I only log on to the machine once?
Or is it required to use something like Selenium to type in passwords. I don't really like selenium for this because:
1. It usually stops working when someone upgrades the browser
2. It seems like alot of work: Need to "reverse engineer" the login page for each site...
Are there any other approaches I can take?
Answering your Questions straight :
Is there some way to synchronize sessions across chrome clients : No, each chrome client will open a seperate session hence you have to login seperately. Inorder to synchronize these sessions you have to use Chrome Profiles and save them on each system.
Or is it required to use something like Selenium to type in passwords : This would be the most optimum way.
It usually stops working when someone upgrades the browser : You can uncheck/disable Automatic Updates to remain at a particular Chrome Browser Version
It seems like alot of work: Need to "reverse engineer" the login page for each site : Login Page for each site will render differently as a DOM Tree. Hence there is no short cuts.
Related
There are two parts to my question of "unattenedness".
The ability to connect to the remote desktop without also having to magically be at the remote site to click the generate key button.
Likewise, not having to be at the remote site to click "Continue" every 30 minutes to prevent the connection from disconnecting.
The fact that I can't seem to find a simple answer when searching the web for help (like being able to use a trusted pin), or even more complex solutions like generating certificates of trust, probably means, "it don't do that".
However, I'm hoping that the problem is that I just haven't figured out how to ask Google the right question yet. Hopefully someone here has some experience and insight into this problem.
Here's what I was doing that made it not not work:
When I downloaded and set up Chrome Remote Desktop (CRD) from the the Chrome Web Store, the chrome account I was logged in with was different on the remote and local computers (I use multiple email accounts for various tasks). This blunder meant that, even though I could change the active account from within CRD, the client and host were not actually configured with the same base Chrome account (email address). So I was being prevented from using the remote access functionality on the “Remote Access” page of the extension (app). Once I corrected that, I was then able to connect using the pin I was prompted to create during setup.
To be more specific:
I completely uninstalled CRD on one of mine boxen
From within the Chrome browser, I logged into same Chrome account as the other box
Then I went back to the Chrome Web Store and downloaded/installed CRD
Then the “Remote Access” page showed the remote computer and let me use the direct access pin
We have a site running to drupal and migrated it to Squarespace. I have to retrieve some pages of drupal site but I can no longer view the site. Do you know any way to get the old content of website on drupal? Please know that we still have access to the drupal box. Any suggestions will be a big help.
Easiest way would be to make the old Drupal site available again through the browser running on a different domain like old.example.com, login into the admin panel and start copy/pasting content.
If you know your way around your computer, know the IP address the old server is running on you could for the time being change the host file of your machine to send requests for your site to the old server and get access to the site that way.
Migrating content by automating the process is also an option, but it is not only time consuming, it requires in depth knowledge of both platforms so is mostly a very expensive solution if you are not able to do this yourself.
But if I read your question, I think the first option is the easiest option. Get a hold of the technical person/party of the server the site is running on and get them to make the site accessible on a different domain.
We have just started to deploy our app over four schools with the server located in one school. The Three schools accessing from outside the system are working fine, but when you access from the school hosting the server, its like the wrong HTML is being returned. In one case, a user had a page returned to her with a different users userid displayed on the page. It also keeps going back to the login page even though your still logged in. Outside of the school all's fine.
Any ideas ?
This is one of those problems where it's difficult to pinpoint the cause without actually being there, or having lots more information. My first thought is that maybe you're using ip based virtual hosts and the NAT (Network Address Translation) is interfering with it.
Edit: could you tell us what sort of caching you have in place? Users seeing each others “logged in” pages without even logging in themselves is a sign that you're caching things that only authenticated users should see.
I've created 2 websites.
Both website have their own database, but there is a user table in both websites that has exactly the same values. What I want to do is make something that can take a user who logs in to website one and automatically log the same user in to website two as well.
Honesty I don't even know how to do it. I've tried to use extra page and login with session and javascript trick but most of the time its not working... especially in IE.
By the way i'm using classic ASP and SQL 2008.
Any ideas?
If you are using classic asp, I assume you are manually dropping an auth cookie that you check on each request?
If so just add this checking code to both sites. You may need to rip it out and put it in a class library that is accessible by both sites.
I am assuming they are on different domains.
On website1 you have a hidden form (possibly in an iframe) with an action pointed at the website2 login handler. If you are not the administrator of website2 then you may run into problems.
Related: http://en.wikipedia.org/wiki/Cross-site_request_forgery
What you're talking about is called Single Sign-On, and it's a well known problem. There are many ways to do it, but the simplest is to set a cookie when a user logs into either site, and to look for that cookie when a user visits either site. If the cookie is present, examine it to find the login name and any other details.
This method isn't ideal. You have to do a lot of extra work to secure (otherwise anybody could just write their own cookie and log in as whomever they want) and it won't work cross-domain (are both sites on the same domain?)
Presuming the credentials are exactly the same, couldn't you use site one's credentials to log into to site two, and visa versa?
I have HostGator Baby Shared Plan . I develop Drupal site on. everything was fine at the beginning, then by the time i go further with development, site started ti work really slow. now it is not working at all. giving my sql errors like TOO many connections, etc...
I created so many blocks, pages with View. so it makes my site to so much depend on database. should not I do that? can it be the reason of my site's no working now.
appreciate helps!!!!
Don't use HostGator. If you're looking for something in the same price range, try DreamHost -- they officially support Drupal on their hosting plans.
Ferran's answer is fine once you're done developing, but you shouldn't devlop with cache turned on or else you won't be able to see your own changes.
Yes, Drupal uses a lot of Database. However, you can cache the results of most Views (check the main screen of each view to enable it) and also there's an option to cache the blocks. It all depends in the content of your views and if users are mostly registered or anonymous.
You can also use modules like Boost which saves static html pages so for anoymous visits your database is not touched at all (just the first time, as the page needs to be generated someday...).
You might also want to check the Views filters, not fetching to many rows at a time (for example fetching a week back for the front page).