File System Respository Authentication Methods?

[former_member244608]

Hello,

I was hoping someone here could either explain to me or point me to some documentation that talks about how file system repository authentication works.

First a little background.

We are running EP5 SP4 w/ KM installed.

It is running on Win2000 Advanced Server SP4

Netware 6.0 SP4 is running our file & print sharing.

Now, in an attempt to connect to our Novell file shares, we have installed Novell's Native File Access which allows a Netware server to appear as a Windows server. This is the only way we have found, that works, to share files on a Netware server through the portal.

Everything appears to be working as it should. But now I am trying to figure out how to restrict access. Since part of the file repository procedure is to setup a network path mount point with a user ID and password that has access to everything, how do you then restrict access per the person that logs onto the portal? Hopefully that made sense.

IOW, say I have a server, NW1, and am sharing VOL1. I am using user ID, SUPERUSER, in the network path settings in KM to mount this share point. This is all well and good and when I log onto the portal and navigate to the KM Admin page and it lists all my repositories, I see everything on VOL1. But if I log on to the portal as JOEPUBLIC, if he had access to the KM Admin page, he too would see everything in VOL1. But I only want him to see what he has rights to on VOL1, but the portal isn't using JOEPUBLIC as the user ID to check authentication on VOL1, it is using SUPERUSER since that is what is set up in the network path setting.

Also, what is the point of setting up a System Landscape Definition, thereby allowing you to customize the portal for your logon, when it doesn't use that?

Hope this made sense!

Thanks,

Tom

[JoergWolf · Accepted solution]

Hi Tom,

if a user has access to the KM admin portal pages, he will always be able to see all repositories (incl. all rights). For endusers (no access to KM admin page), the respective user ID should be passed through to the repository (depending on settings) and restrict authorizations for the access.

Hope that helps a bit.

Regards,

Joerg Wolf