Filesystem Repository Manager - Which Authorizations are required

[Former Member]

Hi Experts,

I have created a Filesystem Repository Manager which is working fine with the Admin User. However, the "normal" user (no admin authorizations) is not able to access the shared folder. I cannot even define user mapping for the system access for this user.

I need to setup up authorizations for this User so that he can access the shared folder.

I need to know which roles or groups the user needs so that I can

1. define user mapping for the system access

2. enable the user to actually see the Navigation iView showing the shared folder

Thanks, Johannes

[LJB]

Hello Johannes,

You need to configure the permissions of the J2EE user as per SAP note 615479. See also:

http://help.sap.com/saphelp_nw70/helpdata/en/54/39c53dba21f750e10000000a114084/frameset.htm

To set up your user mapping you need to create a system in the portal system landscape as per the following documentation:

http://help.sap.com/saphelp_nw70/helpdata/en/f0/64b252473e9a479fcd275c79853620/frameset.htm

http://help.sap.com/saphelp_nw70/helpdata/en/fd/de533e5ff4d064e10000000a114084/frameset.htm

Regards,

Lorcan.

[Former Member]

The shared folder access is working for the admin user, so the sap note is not relevant since this is a user independent issue.

For the user mapping issue: The Windows System Alias that I have defined in the portal is not even listed for the user (it isa listed for the admin, though). So, authorizations semm to be missing...

Aren't there any authorizations (roles, groups) that the user needs so that I the System Alias is listed?

Is there anything else I could be missing?

Thanks, Johannes

[Former Member]

No other suggestions??

[LJB]

Hello Johannes,

Check the 'User Mapping Type' property that you have defined for the system alias, you can set it as 'user', 'admin' or 'admin/user'. You'll find it in the properties of the portal system that you created.

Regards,

Lorcan.

[Former Member]

I have solved the problem that the system alias was not shown for the user. The solution is: Role Everyone must be assigned to the system definition and the iView.

Now I am facing other issues:

The Exception Log is as follows:

Exception ID = 20515128-7707-2d10-0c8c-ab31b3e111b4 com.sapportals.wdf.WdfError
at com.sapportals.wdf.WdfCompositeController.buildComposition(WdfCompositeController.java:688)
at com.sapportals.htmlb.AbstractCompositeComponent.preRender(AbstractCompositeComponent.java:33)...

These seem to be further athorization issues... Can somebody help me there?

Thanks, Johannes

[LJB]

Hello Johannes,

Where/how do you get that error? Can your end users now see the FS repository in KM? You can't tell much from the part of the exception you quoted, is there any other error message given?

If it's still some sort of authorisation issue then you should check again the engine users permissions as per the note and link I gave in my first reply, regardless if your admin users can access the content. Admin users are usually system principals and therefore bypass these permissions. So check over note 615479 again, especially the authorisations 'Act as part of operating system' and 'Logon as a service'.

Regards,

Lorcan.

[Former Member]

I have checked the SAP Note and I have configured the J2EE User correctly and restarted Windows but it still does not work.

Let me post some more Info about my error here:

There is a Warning in the Default Trace:

No group command found for rendering menu HoverMenu for resource /johannes-share; parameter rndCollectionCommandGroup

and two Exceptions:

com.sapportals.wdf.WdfException
at com.sapportals.wcm.rendering.control.cm.WdfProxy.render(WdfProxy.java:1858)
at com.sapportals.wdf.layout.HorizontalLayout.renderControls(HorizontalLayout.java:42)... [see Details]

Exception ID = 309699f7-3b08-2d10-c791-99f8b3320f9e com.sapportals.wdf.WdfError
at com.sapportals.wdf.WdfCompositeController.buildComposition(WdfCompositeController.java:688)
at com.sapportals.htmlb.AbstractCompositeComponent.preRender(AbstractCompositeComponent.java:33)... [see Details]

a part of the complete trace is (I post this since I still assume it is an authorization problem):

at com.sapportals.wcm.repository.manager.generic.security.w2k.W2kSecurityManager.isAllowedIntern(W2kSecurityManager.java:307) 
at com.sapportals.wcm.repository.manager.generic.security.w2k.W2kSecurityManager.isAllowedPrep(W2kSecurityManager.java:196) 
at com.sapportals.wcm.repository.manager.generic.security.w2k.W2kSecurityManager.isAllowed(W2kSecurityManager.java:150)

Again, the shared folder works fine when logging in with admin rights..

Anybody any suggestions?

THANKS

[LJB]

Hello Johannes,

OK so you've checked that the J2EE user has 'Act as part of operating system' and 'Logon as a service' authorisations as well as having 'Full Control' on the content in the file system. I presume you able to do the user mapping for these users as well.

So some other checks:

Is your J2EE user a domain(Global) user?

Have your users carried out their usermapping using the format: <domain>\<user-id>

Are both the portal and remote share in the same domain?

Have the users to which the portal users are mapped sufficient permissions on the remote content?

When you mounted the share in the portal what permissions on the FS did you give the user specified there?

The warning you received in the default trace should not be relevant, if you search the default trace for the user-id that is unable to see the remote file system do you find anything? If not you could increase the tracing for the location: com.sapportals.wcm.repository.manager.generic.security.w2k to get a more specific reason as to why it fails for that particular user.

Regards,

Lorcan.