pls help and suggest to register android (4.4.3) device in wso2iot-3.0.0
I have completed below steps if any correction/recommendation, then please suggest.
Installed CentOS 7 (server os) with 8GB RAM
JAVA_HOME environment variable is set to "/opt/jdk1.7.0_79"
CARBON_HOME environment variable is set to "~/wso/broker"
started server by running below commands
$ ./wso/broker/bin/wso2server/sh
$ ./wso/core/bin/wso2server/sh
$ ./wso/analytics/bin/wso2server/sh
logged in as admin in browser with https://10.0.26.145:9443/devicemgt
Received invitation email with user id and password for newly created user
In agent I am entering 10.0.26.145:9763
now problem is when i enters this user id and password (received in email) in wso2 agent in mobile its not proceeding (rotating continuously). Some times its showing error that "Incorrect User Information"......
Pls help into this......
Agent URL should be 10.0.26.145:8280, From IOTS - 3.0.0, the api calls goes through the synapse gateway.
Related
I have a tomcat server in Azure(Linux RedHat8.1) and DB server in GCP(Centos Linux). I connected tomcat to the DB server, And I successfully opened the URL in a browser and I logged into the website. For the first time successfully login and I give break for 10 to 15min and try to login again, this time it can't be logged in.
I don't know what is the root cause of this issue.
After some time when I refresh the page, it automatically logged in, or after 20 to 30min it can be logged in. (or) after 6 to 12hrs it's logged in or in case restart the
tomcat it's logged in.
But the issue does not come from GCP(Tomcat) connecting to GCP(DB) or AWS(Tomcat) connecting to GCP(DB)
Please anyone help me regarding this issue?
Thanks in advance.
I'm having a server with power-bi reporting service installed and configured on it, and from my front-end that hosts the application, i've got angular 7 with proper power-bi components installed.
Since the report is on the server and it needs authentication to login, i get a user and password fill-in prompt in my website whenever i try to access this report, and after logging in, i can see the data of my report.
I'm wondering how to use Kerberos authentication so that i can set-up that username and password to login automatically without asking the user to enter them every time.
What i've done so far :
I've made and set a few SPN in my active directory, made a user in Active Directory Users and Computer and in it's Delegation tab, i've set it to Use any authentication protocol and added MSOLAPDisco and MSOLAPSvc.3 to it. i've added the user account credentials that i've made to service account and execution account in power bi Report server then i modified the rsreportserver config file to use the RSNegotiate before NTLM.
After trying to solve the issue with the mentioned above methods, i still get a NTLM method in network monitor which is installed in the Active Directory.
Any suggestions how to solve this issue? Thanks in advance.
I tried to make a production set up (WSO2 MB 3.1.0 and WSO2 ESB 4.9.0) on the same VM.
in order to secure my production environment I changed the default admin psw for the admin user to more secure one. At the same time I created a new MB user (ESB) which I used as "a technical user" in ESB jndi.properties
when I restarted my server I started receiving the following exception in the ESB which tried to connect to the MB:
[2016-10-07 16:47:31,427] ERROR - AMQStateManager Notifying Waiters([org.wso2.andes.client.state.StateWaiter#654a6148]) for error:not allowed
[2016-10-07 16:47:31,427] INFO - AMQConnection Unable to connect to broker at tcp://localhost:5673
org.wso2.andes.client.AMQAuthenticationException: not allowed [error code 530: not allowed]
at org.wso2.andes.client.handler.ConnectionCloseMethodHandler.methodReceived(ConnectionCloseMethodHandler.java:79)
at org.wso2.andes.client.handler.ClientMethodDispatcherImpl.dispatchConnectionClose(ClientMethodDispatcherImpl.java:192)
at org.wso2.andes.framing.amqp_0_91.ConnectionCloseBodyImpl.execute(ConnectionCloseBodyImpl.java:140)
at org.wso2.andes.client.state.AMQStateManager.methodReceived(AMQStateManager.java:111)
at org.wso2.andes.client.protocol.AMQProtocolHandler.methodBodyReceived(AMQProtocolHandler.java:517)
I back-traced the problem to the change of the ADMIN psw. When I set it back to the default ADMIN:ADMIN all is working again fine.
any idea why? apparently the psw is not changed on all the places
I followed this article https://docs.wso2.com/display/MB220/Changing+User+Passwords
my configuration xmls does not contain the admin psw however.
thank you very much in advance.
AFAIU, Following are the steps you have followed.
Changed MB default username/password.
Created new user("a technical user") in MB and add these username/password in ESB "jndi.properties" file.
Restarted servers and ESB start throwing auth exceptions.
Things would have gone wrong(at least what I can think of) is as follows :
Somehow you have entered spaces in middle of the username "a technical user"(even it's validated in MB management console)
Solution : Don't use spaces in of usernames.
Even you have created a new user in MB(and added it correctly in jndi.properties file in ESB) you haven't assigned a role which have permission to subscribe to a topic/queue. (This is what most likely you have messed up :))
If you haven't assigned a role which has subscribe permissions to queues/topics ESB won't be able to subscribe with given credentials during transport startup which leads to authentication exceptions.
MB has a role based permission model and if you haven't assigned a user to a role with sufficient permissions user won't be able to authenticate to MB. To verify this theory you can assign "admin" role to newly created user from MB management console under("
Home > Configure > Accounts & Credentials > Users and Roles > Users") and restart ESB server.
Please go through following documentations[1] carefully for more permission/users/user roles related information.
[1]
https://docs.wso2.com/display/MB310/Managing+Queues
https://docs.wso2.com/display/MB310/Configuring+Users
https://docs.wso2.com/display/MB310/Role-Based+Permissions
Im trying to setup WSO2MDM on Nexus 07 tablet.
I have configured web based backend and its up and running.
I followed the guide lines in documentation to set up Client mobile app on the tablet. (Already set the configuration according to steps on documentation and compiled it.)
But When I try to register using tablet it gives me an error saying "Authentication failed due to a connection failure do you want to try again?";
Please advise me how to sort this out.
What's the authentication parameters you tried? In a fresh pack, you may not have configured tenants. So your basic login parameters can be "admin", "admin" as the user name and password. That's basically the super admin's credentials.
First check whether you can enroll the device to that user. Then try with the new user you have created. Always keep the Domain field empty if you do not have a tenant set up. And if you are trying this setup in your local machine, make sure your device and server are in the same network. Android WIFI tethering may help you in that case.
Use this guide[1] when you are enrolling.
[1] - http://wso2.com/library/articles/2014/03/how-wso2-emm-addresses-the-android-challenge/
Thanks
I have WSO2 EMM version 1.1.0 set up. I have the certs all working and everything is playing nicely. I compiled the IOS client and have it installed on my phone via OTA. I am in the process of registering my device. I have a user setup and I have the proper password. I can successfully login from the registration page on my phone and I get the profile downloaded and it has the green "Verified" message on the profile. The problem occurs when I press the install button on the profile. I get a activity spinner at the top of the screen and it says "Installing Profile". It spins for about 30-60 seconds and then I get a message stating "Profile Installation Failed. The request timed out". Any ideas on what would be causing this?
Thanks
Go to {emm_home}/repository/conf/emm-config.xml and chehck whether the following entries are properly pointed to your server.
<iOSEnrollURL>https://10.10.10.174:9443/emm/scep</iOSEnrollURL>
<iOSProfileURL>https://10.10.10.174:9443/emm/profile</iOSProfileURL>
<iOSCheckinURL>https://10.10.10.174:9443/emm/checkin</iOSCheckinURL>
<iOSServerURL>https://10.10.10.174:9443/emm/server</iOSServerURL>
<!-- post url for device tokens -->
<TokenURL>http://10.10.10.174:9763/emm/api/devices/iostokenregister</TokenURL>