Cant Continue Since None or More Than One Block Token Identifier is Found
Hi Vivek,
Since the error message from the log clearly suggests that "The user name or password is incorrect", please double-check whether the affected user's password is correct, or newly changed, or expired.
And if the password is really fine, I also want to collect these details:
1. Does the issue occur to all federated users?
2. Are the affected users trying to configure Outlook from internal environment or external?
3. Is it Forms Authentication or Windows Authentication that is being used?
4. What if the affected users try to create a new Outlook profile? Does the issue persist?
5. Please provide a screenshot of what the users encounter from their Outlook.
Looking forward to your updates.
Thanks,
Allen
1 person found this reply helpful
·
Was this reply helpful?
Hi Allen,
we are able to login to the web app with the same password.
1. Does the issue occur to all federated users?
As its an initial deployment so we created two users in the federated domain.
2. Are the affected users trying to configure Outlook from internal environment or external?
Both
3. Is it Forms Authentication or Windows Authentication that is being used?
intranet-windows
extranet-formbased
4. What if the affected users try to create a new Outlook profile? Does the issue persist?
we tried configuring new profile several times.
5. Please provide a screenshot of what the users encounter from their Outlook.
1 person found this reply helpful
·
Was this reply helpful?
Hi Vivek,
You're able to log into Office 365 with web browsers, which indicates that the authentication process is fine. I notice that you have tried setting up Outlook in both internal and external networks but to no avail. Do web browsers work fine in internal and external networks?
Have tried to change the users' passwords?
In Remote Connectivity Analyzer > Office 365 > Office 365 General Tests, perform aa Office 365 Single Sign-On Test and then click Expand All to share with us the detailed results.
Since it contains your privacy, I have sent you a private message to request it. Please click this link to access your Private Message: https://answers.microsoft.com/en-us/privatemessages/list/.
Thanks,
Brook
1 person found this reply helpful
·
Was this reply helpful?
Hi Vivek,
Thanks for running the test and providing the result in PM. I have checked the test result and found the following error:
Testing TCP port 443 on host sts.<domain.com> to ensure it's listening and open.
The specified port is either blocked, not listening, or not producing the expected response.
Regarding this, please check whether the TCP port 443 has been blocked by your firewall settings.
Moreover, I also noticed that you may have built an Exchange hybrid deployment. Can you please clarify it? If that's true, please make sure that your federated domain has a correct Autodiscover DNS record pointing to the Exchange hybrid server, because I didn't find any related record (the CNAME type) under this domain.
Regards,
Allen
3 people found this reply helpful
·
Was this reply helpful?
Hi Vivek,
Got any updates that you may share?
Thanks,
Allen
Was this reply helpful?
we checked and found that we were able to configure the profile on the external network but not in internal network.
anyway we have dropped the idea of keeping ADFS now as it was not meeting our requirements.
thanks for your support.
Regards,
Vivek
3 people found this reply helpful
·
Was this reply helpful?
seymourharded1956.blogspot.com
Source: https://answers.microsoft.com/en-us/msoffice/forum/all/adfs-token-validation-failed-error/3d281091-5572-4b86-aaf7-11718af1525b
0 Response to "Cant Continue Since None or More Than One Block Token Identifier is Found"
Post a Comment