SUP client key-file location

[Former Member]

We have a client application which uses the sup client for communication with the SUP server.

The sup-client creates a couple of key-files when setting up the connection with the Unwired server.

These files get created in the installation directory of the client.

This can cause problems when the client is installed in a directory where only adminstrator users can write.

In the past it was not possible to change this location where these key-files get created, but we where told this would change in a upcoming SUP version.

Is there any indication from which SUP would contain this feature or if this is already possible?

regards,

Johan Lollinga

[Jitendra_Kansal]

Hi ,

Can you please share your understanding.

Rgrds,

Jitendra

[Jitendra_Kansal]

Hi

I didnt understand with SUP CLIENT word. What exactly it is? And what all client key files you are talking about? Can you give some hint.

Rgrds,

Jitendra

[Former Member]

Hi Jitendra,

the SUP Client is basically the generated Client code that comes from the code generation out of the Mobile SDK. While registering, this code will download two files from the SUP Middleware, a .crt file and a .key file. This is done regardless of you are using End to End Encryption or not.

The Problem is that this file will be downloaded to the place where the .exe file of the Client is located. When you install your Client Code as an Application into the default program path of Windows, the creation of these files is denyied by the operating system.

regards

Carsten

[Former Member]

Hey Johan,

we got the same issue when running an SUP Client on Windows, did you find a solution or a SUP version which supports the definition of a location for these files?

The only thing that I found ,which would hint to a solution, is the doc for Android on End to End Encription:

SyBooks Online

There they configure a path within the configuration of the stream, on Windows, using SUP 2.2.4 this has no effect.

regards

Carsten

[Former Member]

We have not found any working solution for this problem unfortunatly.

I also found the document you link, but it doesn't work on our version either.

We have also been in contact with SAP with regards to this issue and we where told that there is no workaround to change the location of these files and that there are no plans to implement a way to change the location of these files.

Regards,

Johan Lollinga