Handle tailing slashes in configured Authority and Instance

[egeskov]

Purpose

Allow configuration of Instance and Authority with or without tailing slash.
Distinguish valid audiences as specified by Client Id or by Audience Uri - don't prefix prefix audience with api:// if already prefixed.

Does this introduce a breaking change?

[ ] Yes
[X] No

Pull Request Type

What kind of change does this Pull Request introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[X] Other... Please describe:
Input tolerance.

How to Test

• Get the code

git clone [repo-address]
cd [repo-name]
git checkout [branch-name]

• Test the code

What to Check

Verify that the following are valid

• Try configuration strings for Authority and Instance that ends with or without slash.
• Try configuring the Audience using Client Id or Audience Uri (either prefixed by 'api://' or not).

Other Information

[msftclas]

All CLA requirements met.

[jmprieur]

@jennyf19 : interesting proposal to have Microsoft.Identity.Web more robust

[jennyf19]

new List [](start = 37, length = 16)

I think we should do a HashSet<string> here instead of a List<string>

[jennyf19]

would be nice to have test coverage for this, but i think it's related to our larger issue of lack of tests atm. :) LGTM otherwise.

---

In reply to: 583803922 [](ancestors = 583803922)

[jennyf19]

[jmprieur]

Thanks @egeskov

[TiagoBrenck]

@jmprieur FYI this had been taken care in the refactor PR.

[jmprieur]

yes. It's in the renamingUi branch, with unit tests, moreover, now.