This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(217.60000000000002, 7.000000000000001%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAM%3C/text%3E%3C/svg%3E)
Hello All,
we have the following end point enabled on our ADFS 2012 server
/adfs/services/trust/13/windowsmixed
the full url is https://xxxx.xxxx.xxx/adfs/services/trust/13/windowsmixed , however when we try to browse the url on the any browser we get an error
This page isn’t workingIf the problem continues, contact the site owner.
HTTP ERROR 400
what do we to check from ADFS server side for this error and how to fix it.
Regards
Aamir Masthan
400 is Bad Request. This endpoint is not intended to be used by a browser doing a GET. This is to request a token using the WS-Trust standard (you could do it programmatically using the WSTrustChannelFactory).
This endpoint is not even enabled by default in recent version of ADFS.
What are you trying to achieve?
Hello
Thanks for the reply
I am ADFS admin and Yes it was enabled by us manually , on application team request.
we have created RPT for one application, and they are trying to configure something on their side and stated there is some issue on this end point
Regards
Aamir Masthan
That's an odd requirement to use this endpoint in 2020.
I would encourage them/you to use OAuth2 flows (and upgrade to ADFS 2016 at least). Or use WS-Fed or SAML (then no need to upgrade although you should still do it to use the new security features). If you have Azure AD, you can also create a custom Enterprise Application in Azure AD and skip ADFS altogether.