Authorising Users

[Karen Mac]

Re: Authorising Users

IN fact, I just had a headache similar to this in creating an autoresponder for a newsletter, for which I created the table, instead of using theirs. The table created in my sql just fine, but it wouldnt connect to the autoresponder without manually going in and editing the script to connect the two!! I still never got the wrinkles out..and put it on the side for now cuz i have 5000 other major projects to complete too..

Ok thats an exageration, but I do have three other stores which 1 needs product finished, one needs new products added, and all four need link trading done, and press releases to keep up with the big dogs ... Im doing a home and garden show in about 2 weeks, and working on building a NEW store! so .. ok i was only 1500 short.. LOLOL

Karen

[davidundalicia]

Re: Authorising Users

I want users to register on the site (with username and password) at the home page for accessing rest of the pages. Once they register, the access should be automatic & instant. Do I have to create a form to capture their information and then authenticate users (manually or batch), before they can access? But that will lead to time gap between registeration and access & will require admin intervention everytime. How will the Member Login object check and verify the username & password?

I have gone through tutorial at www.vodahost.com/sholaunch.html but got confused or missing some point.

We need to go back to the original question and look at the requirements again.

1)..I want users to register on the site (with username and password) at the home page for accessing rest of the pages.

I read this as being: no login/registered = No entry to rest of site.

therefore
soho home page register/login links to BV register/login system:
which stores username/password
which is only activated by returned email link automatically.

BV authenticates user/password and then passes user back to Soho rest of site.
If not logged in, bv returns to Soho home page..........If there are NO other links from soho home page, where else can they go??

2)..Once they register, the access should be automatic & instant.

Covered by using the BV link as above........................

.................................................. ................................................

Now, give me a thousand reasons why this wont work............lol

[navaldesign]

Re: Authorising Users

David, one question, because i don't really understand what you want to say:

A user clicks on a link to get to the Soho site. He does get there, in the home page. And, there is, ofcourse, a menu bar that allowes him to click and see the rest of the Soho site pages. What will prevent him from seeing the rest of the pages ?

Soho, by default, has the menubar displayed. Also, even if you make the first page without menubar, and use a second page, as "home" page with a menu bar, once one has found the link to this second page, what would prevent him from typing in his browser, directly this second "homepage" URL, and from there visiting the rest of the site?

In my opinion, a password protect script must be able to protect every single page, and this i beleive can only be done by implementing, in each page, a "protection" code.

There is also another way, through a database driven "list" of protected pages, but in this case the links in the menubar have to be built in a certain, not so easy, way.

[Karen Mac]

Re: Authorising Users

David,

The passwords he wants to generate are to access the REST of the site, not the home page. He also wants to avoid having to manually email each member and assigning passwords and access to the database for the PROTECTED PAGES.

Your script will work, in that it will create logins and passwords, no one is questioning that. The problem will be how to get SOHO to recognize them. You have to have a way of having SOHO read the database and the PASSWORDS as the passwords are going to be used to LOGIN to SOHO PROTECTED pages.

Please go see www.grannys-nook.com I think there are two pages accessible to the public, the rest require a password. You could create your login in script and generate passwords all day long, but they wont work in that sign on. Just like your script wouldnt give me access to your cpanel? If I created it and put a page up and said... Ok sign up here so we can all see davids hosting account and see what he is up to. The script will assign passwords ok, but they still wont get into your account.

Karen

[Karen Mac]

Re: Authorising Users

To further clarify. In soho you create protected pages by first making GROUPS. A group can be one person, say a photographer wants to allow only one client to access a page of proofs. He then Makes a page and in page properties assigns the group.. public, member, Mrsipwich, or whatever it is. He then goes to authorized users and creates a user id, user name, password and their email.. etc.. etc, and assigns the GROUP or pages they can then view. These databases are stored within soho's database system.

The reason your system wont work, is because its not writing to these databases. There are three places it must converge, the group or page assignment, the user assignment, and the sign in database itself.

Karen

[navaldesign]

Re: Authorising Users

Third part loggin scripts work like this: you embedd, in the page code, in the very begging, the protection code. If the code sees that the user is authorised (logged in) it allows the continuation of the code execution, if not, it redirects to the login page, where the user logs in (or registers and then logs in) and then, he is automatically redirected back to the page he came from, or to a predifined page.

In conclusion, if there is a way to include this protection code in the Soho pages, then a third party script would work.

I don't know if this is feasible, because i have very litle knowledge of Soho. I will try to find out.

[davidundalicia]

Re: Authorising Users

I took great pains to mention that I have never ever used Soho, so I am following this thread with great interest..............

Logic is logic and most systems are logical, so we have a Soho home page
with a menu which needs a password before one can view any of the other pages on this website.

Required:
automatic system of login without constantly issuing passwords.

Solution:
set up one username and one password in Soho.....
Soho is happy cos now its got something to look at and check for.....

DO NOT issue this user/password to anyone.......(group user/password)

Now......
on Soho home page you have a text or pic link which says "Register Now"

this takes the potential browser to the 3rd party auto username/password
program, which creates and stores relevent details.

After user has verified his/her details AND activated his/her account then and only then will they be issued automaticallywith the Soho (group) user/password to login and view the rest of the site..................

No initial registration = no group user/password issued = no entry to rest of site..................

Soho home page login will now function as required.

[Bethers]

Re: Authorising Users

OK, I know if I was this person - I wouldn't want to have to build in another program to do what I want, but would want it all on the ONE website.

Just my 2 cents. And it can be done by purchasing the plug in - or, I'm sure, by writing your own code that works with Soho.

[Karen Mac]

Re: Authorising Users

LOLOL>. .. Ok I give up trying to explain!!!

David install soho and do this and see if you can get it to work and let me know...LOLOL. But im telling you its like getting windows to run on a linux server :)

You can only do it with software to make it MERGE!

Karen

[Karen Mac]

Re: Authorising Users

And if this worked with only one password user ID, what happens if for whatever reason you want to disallow this member? You have to then reissue the user ids and passwords, cuz they all have the same one. Even if you ban one person theyd still have access.

Karen

[navaldesign]

Re: Authorising Users

I did try, and i think i have found the way to make it work. I will post details later. Now regarding disallow etc, my loggin script has full database administration area, where you can add, delete, ban, suspend ets users. Also allowes to manage subscriptions (if that is a subscription site) etc. let me verify some things and i will come back.

[davidundalicia]

Re: Authorising Users

Stimulating conversations always produce results Karen....lol

Well done George, look forward to your solution.....

Beth, your 2 cents was worth more.......I have now started to take an interest in Soho.........

Now lets ALL have fun...

[Karen Mac]

Re: Authorising Users

David

You're right it has been stimulating, but I think the poor guy who asked to start with is really CONFUSED now and has his bat out to hit us all!

:)

Karen

[davidundalicia]

Re: Authorising Users

On the other hand, he or she may just have learnt a few things about Soho.....

[navaldesign]

Re: Authorising Users

Ok, here it is: please visit www.soho.dbtechnosystems.com

I have password protected the Products and Services pages, the rest are free.

Please note that i have only used a subset of my loggin script, so registering, remind password etc functions are not available.

To loggin use Username "demo1" and password "demo1" . If you do want to register, and see how the script reacts to your own username and password, please visit first http://www.dbtechnosystems.com/register.php

register with your own username and password, and then, go back to the first link i gave you, to visit the soho test site.Please note that you CANNOT have both soho's built in group access autorisation AND this (or another third party) loggin script. This is because Soho's autorisation routine is completely different from our own routine. However, group permissions can be handled directly from our script also, so you don't have to use Soho's. If anyone is really interested, our loggin script supports all types of autorisation: admin, moderator, user, group, guest. It also features subscription payment, automatic suspension if the subscription has expired, automatic activation or reactivation of the account (after the payment has been done), email confirmation (admin's option), user banning, IP banning, automatic subscription expiration notificatio, etc as addon modules: you only get what you need.

What is the process? You add a Custom code block in your Soho page. You need, ofcourse, to upload this code. The code uses sessions to see if the user is logged in or not. If he is not, it redirects him to the loggin page (and, from there, if necessary, to the registration or remind password page). After he logs in, he is then automatically redirected back to the protected page where he came from. As simple as that.