product-is: unable to login to application after upgrading to IS 5.11 with true

Hello wso2 team,

@madurangasiriwardena @JKAUSHALYA @thushaaanthan @pulasthi7 @godwinamila @omindu @thanujalk @isharac @tharindu-bandara

We were using IS 5.10 , because of below error during logout
ERROR {org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/].[bridgeservlet]} - Servlet.service() for servlet [bridgeservlet] in context with path [/] threw exception org.wso2.carbon.identity.base.IdentityRuntimeException: Invalid tenant domain , based on the suggestion from https://stackoverflow.com/questions/46771416/wso2-is-invalid-tenant-domain-when-providing-id-token-hint-to-logout-endpoint, we have enabled the below property in carbon.xml

<EnableEmailUserName>true</EnableEmailUserName> , even without this property email user name was working but throwing the above error . we were using usernames with email as well as without email in 5.10 version which is not working in the new 5.11 version.

With the same configuration in 5.11 version of IS , we are unable to login to the application with the below error , “invalid username!, username should be an email address”

for users logging in using the username without email.

could you please let me know what is that we need to change to make both usernames with and without email working as previous version of IS,

i have tried adding an email domain to the admin user like admin@123.com , but even with this username ,i am unable to login even to IS console as well as my application ,

How to reproduce: Enable property <EnableEmailUserName>true</EnableEmailUserName> in 5.11 and try to login with username and not the email username,

Expected behavior: User should be able to login with username as well as email username,

Environment information (Please complete the following information; remove any unnecessary fields) :

Product Version: IS 5.11
OS: [e.g., Windows, Linux, Mac]
Database:Oracle
Userstore: JDBC

Optional Fields

Suggested labels:

About this issue

Original URL
State: closed
Created 4 years ago
Comments: 18 (5 by maintainers)

Most upvoted comments

@hari819 @dishelt

This is fixed in 5.11.0 after the GA release as an update. You can obtain the updates, if you have a subscription.

rksk on Apr 19, 2023

This issue is fixed now. To get both username and email-username working with <EnableEmailUserName>true</EnableEmailUserName>, please add the following configuration in the deployment.toml file.

[tenant_mgt]
enable_email_domain = true
disable_email_domain_validation = true

sachiniWettasinghe on Jul 5, 2021

Hi @hari819,

now is it mandatory to move to the new configuration model ? , it was all working in 5.9 and 5.10 version .

Please note that it is advised to use deployement.toml based configurations for the latest versions of WSO2IS as we have introduced it for simplified configuration management capabilities and moving away from the fallback strategy to remove deployement.toml and use .XML based configurations.

For your initial question, it seems along with the fixes in https://github.com/wso2/identity-apps/pull/618 and https://github.com/wso2/product-is/issues/8117, the support for allowing both email and non-email usernames has been removed. I will further analyze and update this.

ayshsandu on Dec 18, 2020

Seems like you are referring to old documentation.

Here is the lastest documentation email as username in 5.11.0. https://is.docs.wso2.com/en/latest/learn/using-email-address-as-the-username/#using-email-address-as-the-username

From 5.9.0 onwards we have moved all the configuration to new configuration model. So going forward better to follow the corresponding version documentation.

senthalan on Dec 14, 2020