API invocation fails if resource path has /t/ in super tenant API

[AmaliMatharaarachchi]

Description:

Steps to reproduce:

create a resource with /t/ in the super tenant.
ex resource creating:

1. find/t/find
2. /test/1.0.0/abc/t/new
3. /t/levels

But it is not reproduced if we create a resource as follows.
ex: /find/t/

sample invocation for 3rd example.

curl -k -X GET "https://192.168.1.2:8243/pizzashack/1.0.0/t/levels" -H "accept: application/json" -H "Authorization: Bearer 71bb4024-6d20-3f16-9a02-8d39c41147d6".

it will throw the below error.
<soapenv:Reason xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope"><soapenv:Text xml:lang="en-US">Tenant ID cannot be -1</soapenv:Text></soapenv:Reason>

Affected Product Version:

2.2.0

Environment details (with versions):

• OS:
• Client:
• Env (Docker/K8s):

---

Optional Fields

Related Issues:

Suggested Labels:

Suggested Assignees:

[NethmiRanasinghe]

This issue is reproducing in the latest version