New AuthenticationOptions property in global configuration

[faultcode]

Is it possible to use AuthenticationOptions in the GlobalConfiguration? Like this:

{
  "Routes": [],
  "GlobalConfiguration": {
    "AuthenticationOptions": {
      "AuthenticationProviderKeys": [ "TestKey" ],
      "AllowedScopes": []
    }
  }
}

The reason why I would do that is: the Routes configuration is coming from a Service Discovery, and I want all of them to be authenticated via IdentityServer with key TestKey.

Also, is it possible to add AllowedScopes to a service registered to Consul, and then map it to Ocelot Routes dynamically (same as host-names and ports)?

[faultcode]

Can anyone please provide me with an answer?

[harindaka]

I can confirm that this scenario is not supported (or not working for me atleast) as I ran across the same issue today. Not sure why though

[harindaka]

@TomPallister any thoughts? Authentication does not seem to work if AuthenticationOptions is in the GlobalConfiguration section.

[harshmaurya]

Yes, I think this should be an option. I have to explicitly add the AuthenticationOptions in every ReRoute which is a bit of a risky thing. Because, if it is missed in a single reroute by mistake, user would be able to access the data unauthenticated.

[raman-m]

@faultcode commented on May 8, 2019

Can anyone please provide me with an answer?

I believe the answer to all your Qs is Yes because @jlukawska has prepared a nice PR #1215 .
Could you join to code review also please? 😉

---

The issue has been accepted due to open PR #1215 by @jlukawska

[raman-m]

@faultcode @harindaka @harshmaurya
Code review has started.
Go! 😉

[raman-m]

Assigned to @jlukawska