AW: [opencms-dev] How to build website with public/restricted are a?

[Schmidt, Kai]

Hi Michael, 

I have it working with:

1. Created a new Group "restricted" without parent group
2. I created a folder with Owner Admin-group and group "restricted" (the
same for all resources within this folder )
3. set permissions to rwv rwv --- -
4. Set property "export" of folder to "dynamic"

result:
A user is asked to authenticate (http) before he can enter the restricted
area.

problems I had:
1. When user enters wrong password once, he gets an opencms exception and is
not able to enter the right one before closing all open instances of IE
2. As far as I remember, I also had problems to integrate it into my
navigation...but anyway I have an extra page with normal internal links to
all restricted areas.

But I can live with these problems.


If anyone has a doubt how to solve these problems I would really appreciate
to get more information!

Best regards, Kai




> -----Ursprüngliche Nachricht-----
> Von: Michael Schmitt [mailto:mi.schmitt at gmx.de]
> Gesendet: Donnerstag, 6. März 2003 19:57
> An: opencms-dev at www.opencms.org
> Betreff: [opencms-dev] How to build website with 
> public/restricted area?
> 
> 
> I want to build a Web-Site that consists of a public and a 
> restricted area.
> Is it possible with OpenCms to simply create pages, assign them to a
> special group of users, remove the view rights for the 'Others',
> disable the export for these pages and publish the whole 
> site. And if an
> anonymous user tries to access a restricted page OpenCms shows a
> login page to the user and after he successfully logged in, he will be
> forwarded to the demanded page.
> I tried something like this, but I was not able to access the 
> restricted
> pages
> with a user that is only a member of the groups 'Guests' or 
> 'WebUsers'.
> When I try to access one of these pages, I get a little 
> window that askes me
> for the login and if I fill in the username and password of a 
> user that is
> in
> the group 'Administrators' I will always get HTTP Status 401.
> Probably there is an easy solution for this that I don't 
> know. I read part
> 3.4.9. of the documentation, but it does not really helped.
> I will be thankful for any help,
> michael
>