EP5, SP5 using Logon Tickets.
We've configured our corporate LDAP ids to be "friendly" user names, such as "Jay Brown". Since these ids are not the same in R/3, we looked into the reference system concept. What this delivers is EXACTLY what we need; however, it comes at a huge price that makes no sense to me.
When I map my reference ID to my portal ID through the usermapping interface, the portal will attempt to verify these credentials. Additionally, each time I login to the portal, the portal will verify my credentials with the reference system.
This is a real pain! Why should I have an entire R/3 client that has ALL of out portal users on it? Why can't the Portal issue the ticket based on the fact that the Portal Admin mapped the R/3 id to the Portal id?
- Jay
Hi,
There are many pros and cons for the way we have realized this feature. What I can tell you is that the uid/pw check is only made when you click the save button in the ui (for the single system that has the flag ?r3usernamereference=1? in systems.xml). After that, the R/3 user name is stored and no more connects are made during logon.
For the post EP6 future planning we?re considering about other ways of maintaining R/3 user names (by some kind of mass import carried out by an admin).
Kai.
Add a comment