Login information in Datalogic Browser

Hello,
we launch a web-application with the datalogic browser. The problem we have is that the user cannot log out. Even if the device is shut down, the logon information is kept within the browser and with the next start, the same user is logged in.

So it is not possible to change the user with going into the admin-area and delete the cache.

Has anybody an idea how to solve this problem?

Best regards,
Julian

@Julian_Nelitz,

I will discuss this with the development team of our Enterprise Browser and get back to you.

Drew Hugentobler
L3 Mobile Computer Specialist Support Engineer

Sorry to refloat, but i am on the same situation with 1.11.0.64 browser.

I had already checked the option “clear browser cache on home” but when i click home no data is deleted.

Thanks.

Hi Juan,

Which terminal, Android version, and firmware version are you experiencing this on? This “Clear browser cache on Home” feature was implemented way back in Enterprise Browser build 1.4.x. It looks like it is working on the Skorpio X5 that have in my hand right now. However, I haven’t checked every product on every build, obviously, so a hint about the firmware your product is running may give me a fair chance to understand what is going on.

Thank you,

Scott Kucera

Mobile Computers Specialist Support Engineer

Hi Scott.

Currently we are using Memor 11, OS release: 2.14.29.20260113s and browser 1.11.0.64.

We use Omnissa WS1 laucnher and all the config were deployed using a TAR file generated by scan2deploy, sent and installer via command intent of WS1.

Thanks.

Juan

Hi Juan,

I took some time today to load image 2.14.29.20260113s on my Memor 10 to see if there were any unexpected errors popping up. I did see some permissions errors when using a Scan2Deploy Studio profile to upgrade Enterprise Browser to build 1.11.0.64. I’ll report those errors to my Tools team, but Browser itself is clearing its cache correctly when “Clear browser cache on Home” is enabled. I don’t think the permissions error I saw when applying the S2DS profile are affecting Browser itself.

I haven’t tested this with Omnissa WS1 yet. I’ll look into this on Friday morning.

If you have time, can you do me a favor, please? Can you enable Logger then reproduce the problem you’re seeing once or twice, then disable Logger and send me the resulting log file? I can send you steps, if you’re not familiar with that procedure.

Thank you,

Scott Kucera

Mobile Computers Specialist Support Engineer

Hi Scott, already take some logs. How I send to you the files? Our company blocks most used files sharing platform.

Thanks.

Juan

Hi Juan,

I see in another forum thread that Luiz_Oliveira very kindly provided help to get OEMConfig to configure your Memor 11. That thread is at Use OEMConfig with Omnissa WS1 on Memor 11 A13 . I’m sorry you couldn’t get OEMConfig to work on your Memor 11 using this information.

This forum is better suited for simple information requests, and this issue may require exchanging more personalized information that’s best not shared in a public forum. Our best suggestion is for you to open a case with your local Datalogic technical support at Technical Support - SUBMIT AN ON-LINE REQUEST. You’re welcome to mention my name, Scott Kucera, so that we can provide you better one-on-one support.

When you file your case, please include the firmware you are running on your Memor 11. Please also describe your use case. Are you looking to configure only settings on the Memor 11, or are you also trying to configure other applications too? Which settings are you looking to configure? If you’re trying to configure applications too, what are they? Are you seeing any error messages in WS1 UEM or on the Memor 11? If so, what are they? All this can give us a start on helping you.

Thank you,

Scott

Mobile Computers Specialist Support Engineer