So many configs... Guess the flag wasn't tested. I'll wait and see if Emiliano knows an easy way to fix it.

Yeah, indeed, I only just detected this myself.

I didn't even know this setting/option existed 😅. My understanding was that the base wallet would always ONLY deal with tenant provisioning tasks and nothing else, so the decorators were set-up to function this way.

That being said, I think we would have to move this logic into the tenant_authentication decorator for things to work.

Adding a separate decorator just for this would be also an option and it would be more explicit, however the fact that we'd have to basically blanket apply it everywhere AND, more importantly, the added complexity of having multiple decorators stacked (in the right order) makes me think it is actually not the best option.

Taking a stab at this since it was brought up at today's maintainers meeting