My apologies if this is a duplicate - I have been using IdServer v2 for quite some time with basic setup with web-apps as RP's. I now need to configure IdServer as a Federation Gateway, so that it can accept token from Azure Active Directory.
Under Protocols -> WS-Federation -> I have Enabled, Enable Sign-In, Enable Federation, Enable HRD all selected (except Allow ReplyTo parameter).
Under Identity Providers I have added a new entry called adfs, Type - WSStar and the AADS's WS-Federation Endpoint and Thumbprint. Enabled & Include in HRD both are checked.
I have one client web app setup as RP.
when I navigate to the client web app, I get the redirection to idserver, but I always see just the Username Password login, not the HRD options for ADFS.
Ok, I finally found the solution, just sharing for anyone else who come across the same.
All settings and configs remain the same. Except that I had to use the hrd endpoint in place of wsfed endpoint in the RP web app's web.config. But I had read somewhere not to use hrd ep, so it was a bit confusing to use it or not, in the end it worked out though.
In Azure app, the App Id point to the STS issuer uri. Here all paths point to IdSvr since that will be the RP to Azure. That's it. It works seamlessly now.
My apologies if this is a duplicate - I have been using IdServer v2 for quite some time with basic setup with web-apps as RP's. I now need to configure IdServer as a Federation Gateway, so that it can accept token from Azure Active Directory.
I have one client web app setup as RP.
when I navigate to the client web app, I get the redirection to idserver, but I always see just the Username Password login, not the HRD options for ADFS.
What am I missing?