Forum Discussion

keshavshor4's avatar
keshavshor4
Copper Contributor
Dec 21, 2020

information on FQDN based authentication between client and server.

information on FQDN based authentication between client and server. 1) What are the risk associated with FQDN based authentication and How to ensure security with FQDN based authentication. 2) How to implement FQDN based authentication on Azure.

3 Replies

  • Command0r's avatar
    Command0r
    Iron Contributor
    Dec 21, 2020

    keshavshor4, there is a defined set of known authentication methods and FQDN is not one of them. Could you clarify what are you trying to achieve here?

      • Command0r's avatar
        Command0r
        Iron Contributor
        Dec 23, 2020

        keshavshor4, ok, if I get this right, you're working on the external auth provider implementation and would like to use an FQDN as a redirect URI. You generally set this up in the Active Directory, register the auth providers and your app, verify a domain name, and set it as a Redirect URI. More about this configuration https://docs.microsoft.com/en-us/azure/app-service/configure-authentication-provider-aad.

        Debugging the app locally is not a big deal. Generally, the approach is spinning around configuring your 'hosts' file, which is well-described https://docs.microsoft.com/en-us/aspnet/web-api/overview/security/external-authentication-services.

        Hope that helps :smile: