OCI bowser generates new session with each page load

[Former Member]

Here is a summary of my problem:

I am trying to implement the SAP Open Catalog Interface (OCI) with our eCommerce software, but I am having issues with the Web browser that OCI uses.

Our eCommerce software utilizes the browser session id to identify the user. Our issues is that the OCI browser supplies a new session id with each page load.

The weird part is that if I open a standard instance of IE, access the site, and then access the site though OCI the same session is shared by both the OCI browser and the IE browser. The OCI browser is now able to maintain the session ID as the user browses the site.

Thanks.

[Former Member]

Hi,

Session IDs are always unique and short lived.

For the other part where you open the OCI and the standard instance, session ID is shared because of the cookie information stored in the history of the browser.

May be you an issue a standard user ID and password to puchout the catalog and then bring back items to SRM.

Hope this helps.

Thanks,

Prashanth

[Former Member]

Thank you for your quick response.

I understand that session IDs are always unique, and should only last for as long as the instance of the browser is open.

What I have seen happen is that the session ID will get recreated with each page load with in a single instance of the OCI browser.

When the site is opened in OCI it logs the user in, and then redirects them to the homepage. The problem is that the load of the login page, and the load of the homepage have different session IDs. If the user then clicks on a link on the homepage that page load will again have a different page load. This causes the eCommerce system to see them as separate users.

As I described when I open an instance of IE first it seems to work. This leads me to believe that the OCI browser can read the cookie information, but can't write or create.

I am trying to figure out why the OCI browser keeps generating new Session IDs.

[Former Member]

Can you please explain how the OCI is being punched out from SRM? what are the parameters that you pass on?

Thanks,

Prashanth

[Former Member]

I am basing my setting off the example in section 3.1 of the [OCI documentation|http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e020a283-e6ce-2d10-0ebb-bd4de8c32036?overridelayout=true].

It looks something like this:

URL: <LOGIN URL>

Username: guest

Password: password

HookURL: <RETURN URL>

~OkCode: ADDI

~target: _top

~caller: CTLG

I have tried a few different variation of these parameters, and I always had the session issue.

[Former Member]

The URL given by the supplier for punch out must be broken accordingly for punching out from SRM.

Have you done that correctly? (Since session ID is used as identifier here)

[Former Member]

Hi,

I´ve got the same problem. Have you solve this issue?

Carsten