Skip to Content
author's profile photo
Former Member

Reference System - BIG PAIN... Why?

Aug 27, 2003 at 07:03 PM | 8 Views

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

PORTAL Administration and Development | SAP Composition Environment
Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • author's profile photo
    Oliver Stiefbold
    Oct 01, 2003 at 07:07 PM

    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 comment
    10|10000 characters needed characters exceeded

    • Former Member
      Dec 26, 2003 at 06:59 PM

      Hi

      I am also facing same kind of problem. We have NT authentication on portal but we want SAP user ids to be mapped in portal . We used the r3usernamerefrence method. I have only one SAP system to connect, but when after logging into portal and mapping the user ids and password. I was expecting portal to use logon ticket instead of user id and password, as mentioned in portal admin guide. but when I saw the source of html for my iview which conencts to SAP. It shows the url which has sap user id and password written without encryption. Also I doubt in r3usernameref portal is using the logon ticket for logging in to SAP because I changed the logon ticket inportal and have not imported in SAP, its still logging into SAP.

      Also if I change my SAP password should I have to change the same in portal also.

      regards

      Ajay