login page into my website

S

spirit

Verified User
Joined
Nov 27, 2004
Messages
177
Location
Germany - Bremen
Hello,

I want to create a login page on my website. I already found something on de DA support site but we have many DirectAdmin server.

is it possible to create a login page where the client login with the domain, user and password so that they comes out on the right server?

Tia,
Marco
 
It might, if you setup your servers connected together, and using unique username. However, the easier way is creating another box for choosing server first.
 
spirit said:
is it possible to create a login page where the client login with the domain, user and password so that they comes out on the right server?
Click to expand...
In theory, it is possible to create a DB with clients' login, matching servers as well as other information, and a script (either Php or Perl/cgi) which will fetch and match a client's login with his/her server.
 
Hello,

There is actually a way to do this...

We use the following site for our logins and if there is enough interest I can have the code cleaned up and release it...

http://www.mysitelogin.com

The page should work with any DA box... Try one of your domains and let me know...

Additionally, I believe we started coding for other control panels as well...

If there is interest please let me know.

Also, the site just started a revamp so, let me know your thoughts on the design... It just went up last night and we're still tweaking things... eek!

Thanks, David
 
Of course you can do it that way; it's a simple lookup of the IP#. But if you've got a commercial Secure Certificate and don't want your clients to get error messages, it's not the best way to do it; you'd need the name in which the Certificate was issued.

Jeff
 
jlasman said:
Of course you can do it that way; it's a simple lookup of the IP#. But if you've got a commercial Secure Certificate and don't want your clients to get error messages, it's not the best way to do it; you'd need the name in which the Certificate was issued.

Jeff
Click to expand...

Ahh... Well excuse me for offering something that might work for some people... Obviously, you do not feel it is useful to you...

I'll withdraw the offer and be on my way...

Merry Christmas...

David
 
David,

Of course you should offer it; it may work for a lot of people; it will certainly look for people who don't use Secure Certificates, and that's plenty of DA users. And it will work for anyone who doesn't mind their clients getting the error message.

The problem with the error message becomes evident if/when you try the login from IE7 (and all future browsers will most likely do something similar); it urges you to NOT log in.

So many of us, even who've not considered it before, will have to consider buying a generic cert and giving that out for logins instead of the domain name.

Do you really think I should not have warned of the consequences, and let users find it out for themselves?

There's actually another work around; your code could do a lookup on the domain name, then a reverse lookup on the IP#, to get the name to use for login; then system admins could buy a cert in the name of the reverse lookup (or of course set the reverse lookup to the name used for the URL and the cert).

Jeff
 
skruf;119685 [url said:
http://www.mysitelogin.com[/url]

The page should work with any DA box... Try one of your domains and let me know...
Click to expand...

I tried it...works fine....but I'm mystified....if the user has to remember that his site is thomsplace.com to enter that in the signon screen at sitelogin.com, might he/she just as well remember thomsplace.com:2222 ?

I'm sure I missed something...but I don't know enough to figure out what flew over my head.
 
Yeah, well that's what happens, Thom, as we get old^H^H^Hyounger :).

The idea is you want one screen where your clients can log in but you have multiple servers.

Jeff
 
jlasman said:
Yeah, well that's what happens, Thom, as we get old^H^H^Hyounger :).
Click to expand...

Ah, the ravages of age....but at least I got to enjoy the sex, drugs and rock and roll while I could!

The idea is you want one screen where your clients can log in but you have multiple servers.
Click to expand...

It's still over my head....but I guess it would be usefull if one client had multiple accounts on multiple servers...but I suspect the bulk of them are on one server.

Folks running in the fast lane think up the neatest things.
 
Or if one hosting company had lots of servers and wanted to have one place where their customers could go to login, no matter which machine they were hosted on.

Jeff
 
jlasman said:
Or if one hosting company had lots of servers and wanted to have one place where their customers could go to login, no matter which machine they were hosted on.
Click to expand...

Gawd...I am feeling so thick. My poor simple brain keeps on telling me that if I know my domain name, login name and password....I can log into the system via my domain....it really doesn't matter upon what machine i'm hosted.

Now....if I had mutliple domains and used the same login name and password...then going to a central page that woulld give me a drop down menu of my domains might be helpful.
 
What I'm going to do is give each customer access in their customers area, I know which server each customer is on so this will not be a problem to automaticaly give them the correct login, but as Jeff says I will have to buy a SSL cert to not get IE7 error messages when redirecting ...
 
jlasman said:
It's not about what you can do as a user, Thom... it's more about what you as a hosting company wants to do. If you want to give your users one place to log in.
Click to expand...

Guess it's just me....but if I hosted zerobeat.net with avidnetwork, why wouldn't I simply log on to my own control panel at zerobeat.net, since I know my own user name and password?
 
Hey,

Maybe I can answer a few questions... At least with regards to why our site is there...

Originally we implemented the site as a way to keep clients from having to login to their CP using the IP address when they first signed up... DNS resolution and such. A lot of the coding was hard-coded into the script to fit our servers.

We also use it for support... It is a bit easier to simply type the domain name in the site and be directed to the login page instead of typing the URL with the :2222... Minor, yes I know.

Additionally, doing support for clients it is easier to tell them a website to go to instead of having them go to their site and put ":2222" after the URL... At least that has been our experience.

Also, the site matches our theme/brand... The login page looks like this:

DirectAdmin Login

and if you use "demo_user" and "demo" for the login you'll see the skin matches as well.

As far as uses for the script... Well, if you have multiple servers then you use the script in your website. Obvious reason for that would be to have the login somewhere on your site where you post news or specials... It keeps you in touch with your clients...

David
 
skruf said:
We also use it for support... It is a bit easier to simply type the domain name in the site and be directed to the login page instead of typing the URL with the :2222... Minor, yes I know.

Additionally, doing support for clients it is easier to tell them a website to go to instead of having them go to their site and put ":2222" after the URL... At least that has been our experience.
Click to expand...

I see your logic....I've had very good results with a welcome email that explains how the customer can login via his own domain. I suppose I've been fortunate...not one has been mystified by the :2222
 
You must log in or register to reply here.
Back
Top