Using LDAP auth, password protect one page only..

[rootcomputing]

Hello all,

I am new to the forums, but have reading about a specific issue I have been tasked to complete. I currently use CMS MS to manage an intranet portal and it has been setup to use LDAP authentication. Once a user logs in they can go to any of our internal resources and have their credentials passed on without having to log in again. This has and still works great, but I have been asked to make a single page in which only managers can access it.

Right now I don't mind if all  users can see it, but what I would like to do is have it so that when clicking the link to the management page, the users are either filtered, maybe a management group or so that managers have to log in again. It would be nice to have the first option work, but I don't know how using LDAP affects all of this.

I have seen several postings on password protecting pages and to use some of the already made modules, but I have noticed that these modules take care of the login as well as the password and I assume they work together. Has anyone had any experience password protecting within an LDAP environment? I have looked on in other posting, but haven't found anything similar to my setup. Sorry if this post has already been answered. Feel free to offer any comments or other threads. Thanks in advance!

Verisons:

Apache 2.0
CMSMS 1.2
PHP 5

[Pierre M.]

Hello,

Have you searched the wiki and the forum with Google for "LDAP" ? Some LDAP integration has been working for months.

I'm not sure I understand what you are looking for : authentication ? authorization ? front ? back ? modules ? etc ?
-Are you beginning trying to connect CMSms and LDAP ?
-or have you already made some connection and you are trying to map authorization and groups or so ?

Pierre M.

[rootcomputing]

I have looked around some, but most of what I see is the use of modules that handle both login and password. The setup I have now is once a user logs in their authenticated via our LDAP server. From there the user can browse any part of the Intranet. I would like to keep this feature and currently do not have a problem with it. However, what I would like to do is make it so that certain pages require either A) For the person eligible to view that page to have to log in again or B) looking at the user who is trying to login and comparing that to a list of users that ARE allowed access. If they are allowed then they may see the content, otherwise they can't. I have seen modules that hide content, but some require the use of a login module and a password module (this would conflict with LDAP?)

[Nullig]

I think you'd have to write a custom UDT to control that.

You could try incorporating something like this:

http://adldap.sourceforge.net/


Nullig

[Pierre M.]

Hello again,

aren't you looking for FrontEnd Users (FEU) + CustomContent (CC) + LDAP integration ? I'd see it this way :

Firstly, FrontEnd Users (FEU) + LDAP integration. I don't remember if the current LDAP integration is about FEU or CMSms core users management.
Then, standard FrontEnd Users (FEU) + CustomContent (CC). There are other posts in the forum and visual tutorials in the wiki.

Pierre M.