#698 add :/ in scope regex to match

[abdulkareemnalband]

{{$aadV2Token scopes:https://graph.windows.net/openid clientId: }}
fixes #698

[pschaeflein]

When calling custom apis that are protected by Azure AD, and if using the default values provided in the Azure Portal, you end up with a scope similar to api://<guid>/scope.name. (Or, if following some of the ASP.Net samples, the api://<guid>/scope_name).

In this scenario, \S is a better alternative than simply adding a semi-colon (:).

[drub0y]

Just hitting this myself now which really puts a stop to everything I was hoping to do with .rest files for my API which is secured with custom scopes that necessitate these currently invalid characters. Is there anything we can do to help get this PR pushed through?

While I agree with @pschaeflein change, the current change would at least technically address the issues for a lot of people. We can always do a follow up PR to use \S later.

[pschaeflein]

I've resorted to running a private install based on a fork. I asked about additional maintainers, but no "official" response...

#826

[Huachao]

@abdulkareemnalband @pschaeflein @drub0y thanks for your PR and suggestions, and I have changed to use \S instead, this fix will be published in the next release.

[dracan]

@Huachao - Do you know when this will be released? I've just hit the same issue too, and it's quite a blocker.

Ps. awesome work on this extension - it's amazing! :)