Dynamic authentication scopes

[nlf]

I took the simplest approach that I could think of here. Let me know if anything should be changed.

[Marsup]

Are you sure you don't you want + instead of * ?

[nlf]

Thinking it may be wise to white list the parameters the dynamic scope is able to access, allowing anything on the request seems like asking for trouble

[nlf]

Ok, I think I feel ok about this since it only allows the scope to contain things the user is sending in. This should eliminate the possibility of a malicious user exploiting this feature to leak data.

[hueniverse]

Does this needs to be a function? Why not just inline the logic inside the for loop?

[nlf]

This was because the linter throws a "don't make functions within a loop" warning, so I moved it out of the loop

[nlf]

added the tests you wanted, moved the code to make sure the scope is an array to route setup, and tweaked the loop stuff a little. i kept the logic of the replacing in a function to avoid the "don't create functions in a loop" linter warning.

[hueniverse]

You need to set a flag when a route contains a scope with valid {} template parameter, then only call this replace logic if that flag is set. Otherwise you are wasting cycles for the 99% not using this feature.

[lock]

This thread has been automatically locked due to inactivity. Please open a new issue for related bugs or questions following the new issue template instructions.