Possible bug replacing path values about auth_analyzer HOT 5 CLOSED

Hi Regala
No that is not correct. You confound it with "match and replace" which does not work.
As it is common in API's we use the first section in path to describe the object and followed by the value of the object. In your example the object is "users" and the value is "12345" (or "admin"). Means you want to replace the parameter called "users" with the value "admin". So just type in "users" as parameter name ;-)
Please see also my example on the Readme page: https://github.com/simioni87/auth_analyzer#replacement-location

Have fun!

from auth_analyzer.

OOOOOH. You're totally right, and I overlooked the parameter replacement section for some reason 🙈 Thanks!!

from auth_analyzer.

(p.s. in that particular example in the readme, presenet should be present. Thanks again, keep up the good work ❤️ )

from auth_analyzer.

Thank you too :) Your issue has disclosed the bug that the path replacement does not correctly work if the parameter value does not ends with a slash. As we see in your example GET /api/v1/smart/users/12345/admin/1.1
Will be fixed with the next release.
Thaaanks :)

from auth_analyzer.

Hi @simioni87 , hope all is well!

I've been doing some more tests with the extension and often a scenario I encounter is this:

• Having a replacement string occurring in multiple places, with different "parameter" names
  so e.g. in the url it might be passed as ?organizationId, where as in the cookie it's under org= and in the POST body is id=

In this scenarios the easiest thing to do would be to just apply a "match and replace all" rule on the request, regardless of the parameter name. Is this something possible to do at the moment?

This is a feature I still use heavily on Autorepeater, where the following three options shine:

Let me know what you think, thanks!

from auth_analyzer.