Separate TenantId field introduced on UI login pages

Earlier, the user@TenantId format was used to generate authorization tokens.

Example: xyz@TIBCO, here xyz is the user and TIBCO is the tenant.

The symbol "@" was used as a separator between user and tenant. When a user name string contains "@" (maybe an email Id), error messages were showing on the UI while logging in.

To overcome this issue, Username and TenantId fields are now separated.

Note: For Swagger, you must enter the information in user@TenantId format as the new implementation is not yet supported.

While logging in to the Order Management UI or Configurator UI, TenantId, Username, and Password in all three fields are mandatory.

Oauth Token

When you create an authorization token by using the http://<localhost>:<9091>/oauth/token API, it is mandatory to enter tenantId along with username and password in the request body.

Note: The tenant Id is case-sensitive and you must enter as "tenantId" only. Also, you cannot enter the user name in user@tenantId format anymore.