I have configured email otp in axis2.xml
I can also see in from the wso2is Console.
Updated it through console as well.
I still get this error when wso2is trying to send email:
org.wso2.carbon.registry.core.exceptions.ResourceNotFoundException: Resource does not exist at path /_system/config/identity/config/emailTemplate
at org.wso2.carbon.registry.core.jdbc.EmbeddedRegistry.get(EmbeddedRegistry.java:532)
at org.wso2.carbon.registry.core.caching.CacheBackedRegistry.getGhostResourceFromCache(CacheBackedRegistry.java:225)
at org.wso2.carbon.registry.core.caching.CacheBackedRegistry.get(CacheBackedRegistry.java:198)
at org.wso2.carbon.registry.core.session.UserRegistry.getInternal(UserRegistry.java:617)
at org.wso2.carbon.registry.core.session.UserRegistry.access$400(UserRegistry.java:61)
at org.wso2.carbon.registry.core.session.UserRegistry$5.run(UserRegistry.java:597)
at org.wso2.carbon.registry.core.session.UserRegistry$5.run(UserRegistry.java:594)
at java.security.AccessController.doPrivileged(Native Method)
Also in looking at the registry in wso2is console I see that path as:
/_system/config/identity/email
Which is different from what the code is expecting?
Please let me know if anyone has seen this error.
This issue seems like the emailOTP emailTemplate file does not exists in the registry. Browse the registry by moving into Registry>Browse and Navigate to the /_system/config/identity/email. Verify whether you could see emailotp template there.
Sometime you might have added the emailtemplate in the email-admin-config.xml configuration file. But It might not be added to the registry.
If the template does not exist in registry, Refer this blog for how to add email template via the management console. http://www.securityinternal.com/2016/08/email-templates-in-identity-management.html
Related
When I'm validating the account by clicking the link given in email during account verification process(sign up process), I'm getting below error. Can you please suggest what is causing this error?
enter image description here
In the self-registration config section, there is a configuration for callback validation. It is provided as a regex. Make sure you have configured it properly.
We are using WSO2 Identity Server 5.10.0.
when creating users through Identity Server Management console, If user is already exists we are getting below error in logs and User is not getting added:
ERROR {org.wso2.carbon.user.mgt.ui.UserAdminClient} - UserAlreadyExisting:Username already exists in the system. Please pick another username. org.wso2.carbon.user.mgt.stub.UserAdminUserAdminException: UserAdminUserAdminException
However error message is not shown in IS management console
What is the WUM version of the WSO2IS-5.10 you are using? To find the WUM version of your WSO2IS use the WUM (WSO2 Update Manager)
[https://www.chakray.com/how-install-wso2-update-manager-wum-tool-apply-wso2-patches/]
I tried adding two same users named users in WSO2IS-5.10 but it seems to give me the error message in the admin console. check this image,
To check that there are any other issues is happening and blocking the display of error messages, can enable the debug mode in Log4J.properties file in < IS-HOME >/repository/conf folder. And check the link below to see how to set up Log4j.properties file.
[https://medium.com/identity-beyond-borders/enable-logging-in-wso2-identity-server-with-log4j2-4b2ef1374656]
I've changed the wso2carbon.jks keystore to my own store and my CA signed cert is working fine via a remote browser for https. However when I try to change the admin password via the carbon management console UI and restart the API manager I get problems with:
AMQConnection Unable to connect to broker at tcp://10.16.0.5:5673
org.wso2.andes.AMQException: Error occurred while establishing a connection
I'm running 2.0.0 of API manager on Ubuntu 14.04
I don't have enough points to comment on a similar issue:
WSO2 API Manager - Error changing admin password
but happy to experiment and isolate this bug. I could try to change the admin password for all references in xml files under conf if needed.
Please advise on the best way to change the admin password for API manager. I'm happy to do a clean install and see if I can just change the admin password. Please advise if I should use the UI or change in repository/conf files.
Search all xml files with "admin" references. What I can recall is, api-manager.xml, user-mgt.xml, identity.xml, etc.. You may also check out the related wso2 doc.
I've just worked through this issue with WSO2 support. In my case it had to do with the content of the password. I used the same admin password for v2 as I did for v1.10 but apparently the different frameworks in v2 has a problem with special characters in the password. More specifically, a '#' character. The link below was provided as a reference. Upon changing the admin password, both in the console and in the user-mgt.xml file, and restarting the product, I am no longer experiencing the exception.
https://wso2.org/jira/browse/APIMANAGER-4991
I am trying to add service in wso2 governance registry 4.5.3. When I go in to index.jsp and try to add service by clicking add service which directs to add_edit.jsp and trying to give Name, Namespace and WSDL URL and try to save, its giving me "Failed to add the artifact, Special characters are not allowed in the name fields". Can I know what's happening and what I need to do ?
I have added the same service with exactly your details. (JDK 1.7 and Windows 7 with Chrome browser), Can you see if the same service exists in the Registry. I could reproduce it when i have the same service in the registry and try to add once again with the same name.The Error message displayed is misleading and it will be fixed in future release.
I have a situation where I need to setup a standalone version of wso2 Identity Server and have that act as the SSO provider into all of the products in Stratos.
Currently I have Stratos Identity Server configured so that I can login via the standalone Identity Server, using admin.
However, if I use another user I either
get a "Authorization Failure"
or cannot login.
First Question
1) I have the same user created in both Identity Server (that is not admin). Why would I get the "Authorization Failure" ?
Second Question
2) Why is it I can not even get to the "Authorization Failure" problem if I have a user created with username in format of user#domain.com ?
UPDATE:
I figured out that if I remove the property tags in user-mgt.xml that reference the usernames with regular expressions I am able to create usernames in the format of name#domain.com. But I am still unable to use that username to login, the error log says that the account has not been activated.
I also created two instances of wso2 identity server and configured them in such a way to test being able to use one to login to the other. I was able to do this by making sure that the same username and password was in both servers list of users. This way I do not get the "Authorization Failure"
The answers I came up with.
1. I need to have the same username and password in each Identity Server.
2. I cannot have format name#domain.com unless I have Multi-tenancy configured. Otherwise wso2 will try to find the ACTIVATE field in the Tenant table and not find it.
UPDATE: I got this installed and configured and it turned out that I now get another error about
Issuer details are not valid. Issuer details should be registered in advance
So my answer turned out not to to be valid.
I wonder why I get this new login failure?
UPDATE RESOLVED!!:
I resolved this problem by downloading just the wso2 stratos IS 1.5.2 package. I installed it. Configured with same configuration I was using before. Now I can login without problems across domains.