UserAuth handlers not evaluated in document order

[rido-min]

"UserAuthorization": {
  "AutoSignin": true,
  "Handlers": {
    "bad": {
      "Settings": {
        "AzureBotOAuthConnectionName": "bad"
      }
    },
    "graph": {
      "Settings": {
        "AzureBotOAuthConnectionName": "MCS",
        "Title": "SigIn for Sample",
        "Text": "Please sign in and send the 6-digit code for MCS"
      }
    },
    "github": {
      "Settings": {
        "AzureBotOAuthConnectionName": "GH",
        "Title": "SigIn for Me",
        "Text": "Please sign in and send the 6-digit code for github"
      }
    }
  }
}

},

and then calling GetTurnToken returned a graph token

@MattB-msft saw this behavior

[tracyboehrer]

I need more info on this. Which sample are we talking about? Matt brought this up once, but he had a bad configuration, and it was defaulting to the first handler which just happened to be graph. The stack itself doesn't have any hard coded values.

[tracyboehrer]

I see what the issue is. Got it. These are stored in a dictionary, which is sorted.

[tracyboehrer]

@rido-min @MattB-msft This is tricky. IConfiguration has already loaded appsettings, and the handlers are in a dictionary and document order is lost.

1. Switch to an array which will break things
2. Require DefaultHandlerName
3. ??

[rido-min]

Can we leave configuration aside for a moment and start with a CodeFirst approach? this will allow us to better understand the different cases with or without a default handler, auto vs manual, etc.

[tracyboehrer]

Code first would have the same issue. Code first would work if we changed to use a List internally though. With IConfiguraiton, it has already been loaded as a Dictionary. Matt believe he knows the mitigation for that.