If you are using Azure AD authentication, the token lifetime for XWC matches that of Azure AD (which is about 90 minutes). After that the XWC application will look like you are logged out. If the attempt to print a job, the client will silently refresh the token without any user interaction.
If you feel something is not working properly, please submit a support ticket for futher help.
We are also experiencing the same issue, after installation our users complain that they cant print afterwards.
Thats because the user is not logged in sometimes this is the the case.
Also our clients experiencing a token expiration after 2 hours really annoying to login every day for like 5 times to print a job.
Do you have that aswell or not?
The document you mailed me describes only how to configure SSO, but as i said, SSO is already in-place and working fine.
The only thing that needs to be done is triggering the Workplace Cloud Client to sign-in so the enduser does not have to manually do "rightclick the icon and click on Sign-In".
I will contact your privately to obtain some more information.
Is there a command line switch for JobSubmission.exe which will trigger the Sign-In-Click in the UI?
We noticed that when we startup the Xerox Workplace Cloud Client (Jobsubmission.exe) it does not automatically try to sign-in (for the first time). We use an ADFS SSO configuration so our customers do not have to fill in their company mail-address but when the user starts the client they are still not signed in. So how do we trigger that automatically?