Changing user store - what's the impact, what are the pitfalls?

[Former Member]

Dear all,

we're thinking into moving the userstore from portal DB to ABAP backend (or maybe to LDAP). I could not find any valuable documentation regarding aspects like complexity, costs, required ressources, impacts, and pitfalls, regarding portal content.

Now I got told that especially content managament (KM) could be a source of serious problems becaus of documents being linked with old unique user-ids, which after moving the user store wouldn't be valid any longer.

Installed version is EP 7.0 w/ EHP4.

Has anyone already tried this, or has other experience with this matter?

Thanks in advance,

Chris.

[Former Member · Accepted solution]

Dear Christoph,

About which change i would switch to ldap because if you change to abap then never return back, And besides, would have access to the portal synchronized with the network, and users only handle a username and password.

With regard to the problems this can bring if you keep the user id equal you don't have problems, but if you change it you loose the reference to their things stores.

Regards.

[Former Member · Accepted solution]

Dear Damian,

unfortunately, management favors the ABAP backend approach, and I have little influence in that matter.

However, we got told, that there could even be problems contentwise (content management).

I understand your experience is different from that, and there are no problems whatsoever related to the content?

Thanks,

Chris.

[Former Member · Accepted solution]

Chris,

As i tell you previously, if you don't change the user id, you don't have any problems with km functionality.

Regards.

[Former Member · Accepted solution]

Dear Javier,

Thanks a lot!