I created a jar based from the link https://svn.wso2.org/repos/wso2/people/pushpalanka/SampleCustomeUserStoreManager-5.0.0/
a)Copied the jar into dropin folder and mysql driver in lib folder,
b)Started the server and clicked on Add UserStore, Selected CustomUserStore from the drop down and created it with all mysql connection details
c)When i clicked on Users and saw the test.com/dinuka and test.com/malinda user, changed the permission to login and logged out as admin.
d)When i am trying to login as test.com/dinuka-dinuka, I get there error as [2020-02-25 17:08:53,712] ERROR {org.wso2.carbon.core.services.authentication.AuthenticationAdmin} - System error while Authenticating/Authorizing User : Error when handling event : PRE_AUTHENTICATION.
I am using wso2is 5.3
Subhash
Related
I have added an Active Directory to the carbon console to connect to WSO2 API Manager , i have successfully read the users list but when i try to get the informations of each user i got error error while loading user profile metadata .
We are getting below message in error log:
"There was an error while verifying the token. Either the session timed out or un-authenticated access is suspected."
When ever we are trying to update any setting or create new scheduler/gateway, it is redirecting us to login page.
Error While Updating any setting in CF Admin
I'm unable to configure gdrive for rclone, giving 400 error.
According to this post this error message may be caused by using an old version of rclone. Try installing the latest version if you haven't already done that.
Also you shouldn't post your client ID and secret. You should revoke them and re-create them.
I am using rclone 1.60, I still got the same error but I fixed it. You need to add rclone's Redirect URL to the Authorized redirect URIs section of the OAuth 2.0 Client ID that you created for rclone (in the Google API console).
First create your own client ID as described on the rclone website. Make sure it has a secret - click 'Reset Secret' if it doesn't. Remember to save after creating the secret.
Then you need to get the redirect URL:
Start rclone config and proceed through the wizard, giving it the client ID and the secret when it asks for it.
Continue with rclone config until it gets to the auto config part of the wizard (Use auto config?). Answer 'n' to this question.
In its output rclone gives you a command to execute that looks like this: clone authorize "drive" "XXXX". Execute that command in another terminal session.
The rclone authorize command will cause the Google Accounts page to be opened, which gets the error message Error 400: redirect_uri_mismatch
In the rclone output is this text: Make sure your Redirect URL is set to "http://127.0.0.1:53682/"
Now you need to add the redirect URL to the Client ID's Authorized redirect URIs.
Go to the Google API console
Click on 'Credentials' in the left part of the screen.
Click on Client ID in the section 'OAuth 2.0 Client IDs'.
Put the Redirect URL in the section 'Authorized redirect URIs' and click 'Save'.
Complete the authorization process:
Go back to the rclone authorize session - in its output there will be a line that starts with 'If your browser doesn't open automatically...'. Follow the link in that line. The web page that opens will say 'Success!'.
The rclone authorize session will have produced a token. Copy that token and paste it into the rclone config session (which is waiting for a token).
Complete the wizard. The remote should be setup and working now.
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 have installed WSO2 identity server 5.3.0 in our system and tried to establish external LDAP connection using steps provided by LABKIT.pdf.
I have successfully configured "apache directory studio" on my windows server 20008 R2 Stand. To communicate or authenticate to "Active Directory" using Bind DN and password
Bind DN : CN=Administrator,CN=Users,DC=orap,DC=co,DC=in
Bind Password : Psas#2017!!
after configuring necessary settings in a file "user-mgt.xml" for external LDAP settings.Then restarting services "./wso2servr.sh" shows embedded LDAP settings disabled and External LDAP connection successful, but login page of WSO2 can't able to log in using
default admin login
LDAP Username and password.
How to solve this issue in order to communicate our own LDAP server to WSO2 IS?
By looking at your question it seems you haven't added the admin user or pointed an existing admin user for the Identity Server. You can do this via <AddAdmin>true</AddAdmin> and adding a new admin user with new password in the user-mgt.xml. Or else you can point existing user in you LDAP server as an admin user in the <AdminUser> section in the user-mgt.xml
You need to setup your external LDAP connection as a secondary store. What you define in 'user-mgt.xml' becomes your primary store. Your primary store should be a JDBC store in this instance since you're disabling embedded LDAP. If you do it this way, you'll be able to login with your default admin login. Don't forget to disable the admin settings at the top of user-mgt.xml once you start your WSO2 IS for the first time.