You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Each tenant should have a setting for which wallet address prefix they are allowed to use. For example, in the context of JOPACC, an example would be:
Bank 1 (Tenant 1):
Prefix/range: https://jopacc.com/arabbank/ https://jopacc.com/arabbank/<user>
Bank 2 (Tenant 2):
Prefix/range: https://jopacc.com/abcbank/ https://jopacc.com/abcbank/<user>
If a tenant tries to create a wallet address with the incorrect "prefix" or "range", then we should throw an error.
We should store this prefix/range in the tenant settings.
During wallet address creation, we should check whether the non-operator tenant is trying to create a wallet address with the correct URL. Be wary of slashes.
url field was replaced with address field, because now with range in wallet address, it is possible
for the caller, to specify just the portion of the wallet address url. There is no need to specify
the whole url in order to create wallet address.
#3278
Context
Each tenant should have a setting for which wallet address prefix they are allowed to use. For example, in the context of JOPACC, an example would be:
Bank 1 (Tenant 1):
Prefix/range:
https://jopacc.com/arabbank/
https://jopacc.com/arabbank/<user>
Bank 2 (Tenant 2):
Prefix/range:
https://jopacc.com/abcbank/
https://jopacc.com/abcbank/<user>
If a tenant tries to create a wallet address with the incorrect "prefix" or "range", then we should throw an error.
We should store this prefix/range in the tenant settings.
During wallet address creation, we should check whether the non-operator tenant is trying to create a wallet address with the correct URL. Be wary of slashes.
tenantSettings
table in backend #3127Todos
The text was updated successfully, but these errors were encountered: