error:The authentication endpoint Username was not found on the configured Secure Token Service!
1. Install fix in http://support.microsoft.com/kb/2827748 on ADFS server.
2. Restart ADFS server. In the background, the fix would have allowed ADFS to publish mex endpoint in the ADFS federation metadata.
3. Log on to CRM server.
4. Rerun the “configure claims” and “configure IFD” wizards of CRM. Rerunning this will cause CRM to consume the healed ADFS federation metadata and populate the correct mex value in the DB table.
5. To be sure,please run the below SQL query against the MSCRM_CONFIG.
select activemexendpoint from federationprovider
Ensure that it shows a URL similar to:
https://<ADFS STSHOST>/adfs![]()
rvices/trust/mex
6. Reset IIS on CRM server to destroy rebuild and cached content in IIS that was based on the old DB values.
7. Configure outlook client.
1. Install fix in http://support.microsoft.com/kb/2827748 on ADFS server.
2. Restart ADFS server. In the background, the fix would have allowed ADFS to publish mex endpoint in the ADFS federation metadata.
3. Log on to CRM server.
4. Rerun the “configure claims” and “configure IFD” wizards of CRM. Rerunning this will cause CRM to consume the healed ADFS federation metadata and populate the correct mex value in the DB table.
5. To be sure,please run the below SQL query against the MSCRM_CONFIG.
select activemexendpoint from federationprovider
Ensure that it shows a URL similar to:
https://<ADFS STSHOST>/adfs
6. Reset IIS on CRM server to destroy rebuild and cached content in IIS that was based on the old DB values.
7. Configure outlook client.