In the case where a user would be logging in using a custom domain (domain\email@example.com). they could use their own individual Office 365 credentails. However, if you are following the suggestion in the previous post (create an account directly in Office 365 to be used on the Xerox device), then you would have to contact your Office 365 administrator for the account credentials.
What would the password be?
Thank you for the post.
Yes, that would seem to work for ADFS customers as a workaround to connect to O365 via the App.
The App. also supports custom O365 domain accounts. So, if a client happens to be using that configuration, their login creds would be similar to: domain\firstname.lastname@example.org
Note: the domain and customerdomain do not necessarily match. It depends on how the account was set up.
Thank you for sharing this information!
I know this is > a month old but becomming a more popular subject, so figured I would follow-up...
For users of O365 with ADFS or using any other SAML-based identity provider for O365, it seems the Xerox App can not handle authentication...
HOWEVER, as a workaround, I've found you can have an O365 tenant administrator create an account directly in O365 specifically for the Xerox device(s) to use.
Login creds would be: AccountName@TenantName.onmicrosoft.com
Seems to be a workaround without having to leverage ADFS or other federated identity providers. Not ideal, but seems to work if you use the entire onmicrosoft domain in the userID path.
OK I know it's not supported, but can anyone explain why? This is the first question I'm asked after informing a customer (usually large, for us) that they cannot use the app because they're using Active Directory Federated Services (ADFS).
There are several reasons for ADFS authentication to fail, but the most popular cause I've seen is using a non-SNI capable client. Is that the reason? Are they failing to login because they are seeing connection resets and multiple certificates?