BOBJ Auto User Import does not create users correctly

[former_member648389]

Hi,

We are facing a new issue suddenly in BOBJ, where when a new User ID is created in our HANA BW system, from which BOBJ gets its user data, the user ID is getting created as <BWSystemID>~<Client number>/<User ID>. This is causing authentication issues when the user is executing Webi reports. At the moment we're fixing this issue by removing all characters to the left of <User ID> and then saving the ID, but since this is a manual workaround we would like to see if there is a permanent fix.

We're using SAP Authentication. The current version of BOBJ is 4.1 SP10 Patch 9 or 14.1.10.2870

Our BOBJ team says that there was no recent upgrade or patch update, but I'm not sure if they're entirely clued in or just trying to evade responsibility.

[BasicTek]

you can post a ticket # out here it can't be accessed by anyone it's just 4-6 digits

[BasicTek]

That's correct, if any users are left in the system after the registry key is added they will not be updated, and we have seen other complications such as role mapping problems.

This may present other issues if your users do not have other aliases as removing them will delete any user data they have, and removing roles could remove any security settings set on the role.

Aliases can be created https://apps.support.sap.com/sap/support/knowledge/preview/en/1401058

and for roles, we always suggest when using 3rd party plugins to set security on enterprise groups and add the 3rd part groups to them (and they inherit the security)

I did not think of the possibility that expanding BI could put you in this situation, if you have a support ticket this issue may be something that development might need to look into.

-Tim

[former_member648389]

Hi Tim,

Thanks for your reply. I think the addition of aliases to keep the user data is a viable option, but SAP does not seem to be supporting the entire solution themselves as it's not an official code, and hence it may not be possible for me to convince the client on its usability.

Removing roles may also be an issue. I'm not sure if we have created any custom roles, I'd have to check. How does reporting folder security work if we delete the roles. Would we have to add back all of the folder security and reports to folder mapping if we were to delete the roles?

I have raised an OSS Message, perhaps I could PM you with the message number so that you may be able assist in redirecting it if in case it's something that development might need to look into?

[BasicTek]

How the users are mapped in is determined by https://apps.support.sap.com/sap/support/knowledge/preview/en/1343537

This isn't a setting that suddenly stops working. It also isn't one that is easy to enable, It requires the SAP users/roles to be removed (make sure there are none left in the system as this may take time), add the registry setting and then add the users/roles back. If this is not done in the proper sequence any users that are in the system will be problematic, not likely updated, and other issues have been known to occur as well.

-Tim

[former_member648389]

Hi Tim,

Thanks. I did find that note afterwards so it did help me to point towards the root cause of this issue.

Apparently, there were new servers added to the BOBJ application where the registry fix was not executed, this was done a couple of months ago. The registry fix was executed on the existing BOBJ server a few years ago, but the new servers were probably using the old registry settings.

If I understand you correctly, I need to remove all of the users and roles that were auto imported into BOBJ, execute the registry change, and then schedule a new auto import?

[ayman_salem]

see

KBA 1781355 - How to automatically alias SAP users from different multiple system to users existing in BI 4.0

https://launchpad.support.sap.com/#/notes/1781355

and related

KBA 1343537 - Displaying SAP usernames in the USERNAME format

https://launchpad.support.sap.com/#/notes/1343537