802.1x Cedential Caching for Server Access

My customer will be using a CE5 device with 802.1x PEAP authentication.  They may also use TLS authentication as well.

 

The devices are intended for Gift Registry users , so the customer requires no user intervention for sign-on to the wireless network and the associated file server the device needs to send the uploaded gift registry lists to.

 

For PEAP, The device will authenticate to the 802.x network with a “service account”.  This service account will be in the same domain as their kiosk server they want to upload to.

 

The normal course of operations for the Gift Registry device is real time RF communications.  In the event that the device does not have RF access to the Gift Registry Server, the device will have a batch mode.   When in this batch mode, the device will need to “silently” connect to a server in the domain and upload the batch file without a server credential box.

 

We are currently getting prompted on the CE5 device for server logon credentials.  How can we get the 802.11x credentials properly cached so that we do not get the “Logon To Network Server” sign in box for a server that is in the same domain?

 

Please see the attached doc for screen shots of the server login box and Fusion Set up

Christopher Sather
attached doc

attached doc
Vote: 
Vote up!
Vote down!

Points: 0

You voted ‘up’


David Meyer
Chris, The cached password is

Chris,

The cached password is only for PEAP (802.1x) not for File sharing.  The loging dialog you see is for Windows file sharing, and thus cannot be cached by Fusion.  I am not sure if Microsoft has a way to cache this information.  It sounds like you ARE properly caching the Fusion credentials, but even though they are the same credentials as the file share, the device does not know that.

-Dave

Vote: 
Vote up!
Vote down!

Points: 0

You voted ‘up’


Log in to post comments