Against what frontend users should be authenticated?

Post by **Oliver Georgi** » Sun 11. Jan 2004, 15:17

I have added a new checkbox in site structure editing which is used to mark this structure level as "visible only for frontend users". An article and/or content part based extended version will be available later (but it is simple).

It will be a very poor solution at the moment. But it is planned to be extended for use of special frontend users/usergroups later.

Please fill in the poll or write some thought of your own.

Thank you
Oliver

frold · Post by **frold** » Sun 11. Jan 2004, 15:31

I do not understand the Q!

vvo · Post by **vvo** » Sun 11. Jan 2004, 15:34

I believe Oliver means that your website could contains parts/articles only viewable after login (at the frontend). Some sort of protected area or intranet usage.

The frontend user should be no backend user IMHO.

Greetz,

Johan.

MarcoB · Post by **MarcoB** » Sun 11. Jan 2004, 15:44

For all dutch viewers,

http://www.phpwcms.nl

waggis · Post by **waggis** » Sun 11. Jan 2004, 16:11

a kind of extranet or members only section ? great thing!

waggis

tcm · Post by **tcm** » Sun 11. Jan 2004, 16:20

Könntest du das ganze nochmal auf deutsch erklären?

Alexander Schlegel · Post by **Alexander Schlegel** » Sun 11. Jan 2004, 16:25

Ich hoffe, dass ich jetzt richtig gevotet habe, wenn Lösung 2 für einen geschützten Bereich für User von außen steht ... Naja, wird schon stimmen ...

Gruß
Alexander

waggis · Post by **waggis** » Sun 11. Jan 2004, 16:47

i try to explain what oliver means:
a frontend user can have acces to a kind of restricted area of the site.
the question is: where are those users regitrated ? in the backend like
administrators and publishers or in the frontent (new table
in the database) ?

my own wish is: frontend (in a new table in the database).

oliver, do you also plan user groups ? by restricting the pages where
users are allowed ? e.g. special pages for customers / for resellers ?

waggis

frold · Post by **frold** » Sun 11. Jan 2004, 16:59

waggis wrote:i try to explain what oliver means:
a frontend user can have acces to a kind of restricted area of the site.
the question is: where are those users regitrated ? in the backend like
administrators and publishers or in the frontent (new table
in the database) ?

my own wish is: frontend (in a new table in the database).

oliver, do you also plan user groups ? by restricting the pages where
users are allowed ? e.g. special pages for customers / for resellers ?

waggis

now I get... well I have chosen frontend (in a new table in the database) because I understand feature like this:

On the frontend it will be able for users to login and then see pages that are not visible for "normal" users. This would be good for me, eg. if the site have a phonelist that is not going to be public etc.... This would be a VERY greate feature I think. This way you can also hide content for search engines etc....

hblaschka · Post by **hblaschka** » Sun 11. Jan 2004, 17:02

Just a little reminder:
Oli, try to code a way that enables us to extend the code to other authentication-sources like NDS/ADS via LDAP in the future....

frold · Post by **frold** » Sun 11. Jan 2004, 17:13

frold wrote:now I get... well I have chosen frontend (in a new table in the database) because I understand feature like this:

On the frontend it will be able for users to login and then see pages that are not visible for "normal" users. This would be good for me, eg. if the site have a phonelist that is not going to be public etc.... This would be a VERY greate feature I think. This way you can also hide content for search engines etc....

and you can share internal files (there aren´t going to be public) etc....

Actually the point of the backend right now is not the way I would like...

Functions like internal chat and messages should be visible via frontend after you login and the backend should ONLY be accesible for the admin.

Right now you mix admin and users using the same backend - and that is not optimal ....

Just what I think, but I´m not going to share my the backend with 10+ users so actually I don´t care

- but that was my opinon... and I will stil use phpwcms anyway!!

Post by **Oliver Georgi** » Sun 11. Jan 2004, 17:26

I have absolutely no experience in solving this at the moment (LDAP). So this can be extended later - now it has to work

as described.

And I've made a decision. For faster implementation and more consistent developement it's recommand to have only 1 user database. But this will be extended for handling frontend and backend users.

I will create an external authenticate/frontend login check. This can be changed easy for your needs - also athenticate against other non phpwcms user databases.

Multiple frontend permissions can be included later. Now the have of such login process would be an important step.

Oliver

Florian · Post by **Florian** » Sun 11. Jan 2004, 17:31

Hello together!

It might be telepathy. I started today buliding a Frontenduser solution for phpwcms.
I'd choosed the second solution. I made a table with this design:

Code: Select all

CREATE TABLE phpwcms_feuser (
  feu_id int(11) NOT NULL auto_increment,
  feu_login varchar(30) NOT NULL default '',
  feu_pass (50) NOT NULL default '',
  feu_email varchar(150) NOT NULL default '',
  feu_thislogintime(14) NOT NULL,
  feu_lastlogin timestamp(14) NOT NULL,
  feu_overalllogin int(4) NOT NULL default '0',
  feu_active int(1) NOT NULL default '0',
  feu_lang varchar(50) NOT NULL default '',
  feu_title varchar(50) NOT NULL default '',
  feu_firstname varchar(50) NOT NULL default '',
  feu_lastname varchar(100) NOT NULL default '',
  feu_company varchar(100) NOT NULL default '',
  feu_street varchar(120) NOT NULL default '',
  feu_city varchar(120) NOT NULL default '',
  feu_zip varchar(50) NOT NULL default '',
  feu_country char(2) NOT NULL default '',
  feu_fon varchar(30) NOT NULL default '',
  feu_fax varchar(30) NOT NULL default '',
  feu_mobile varchar(30) NOT NULL default '',
  feu_newsletter int(1) NOT NULL default '1',
  PRIMARY KEY  (feu_id)
) TYPE=MyISAM COMMENT='Table for the frontend user data';

So you've got all basic claims data you maybe need.
Overall it's a VERY IMPORTANT and usefully option which will hopefully be published shortly

Cheers,
Florian

adriano · Post by **adriano** » Sun 11. Jan 2004, 19:15

Grundsätzlich sollten für den Frontenduser möglichst viele Bereich nutzbar sein mit nur einem Login pro Website. Ich sehe schon auf meiner Site mindestens vier verschiedene Logins: Einmal phpwcms, einemal phpbb, einmal die Bilddatenbank Coppermine und zum Schluß noch das Projektmanagment für meine Kunden.

Also, je mehr ich die Daten zentralisieren kann auf meinem Servier, desto besser. Schließe daraus bitte meinen Wunsch, Oliver.

fitus · Post by **fitus** » Mon 12. Jan 2004, 17:36

wie wärs mit beidem, das sich user vonselbst registrieren können aber auch nur vom admin einen zugan erhalten können.

Against what frontend users should be authenticated?

Against what database frontend users should be authenticated?

Against what frontend users should be authenticated?

phpwcms.nl