I have successefully installed WSO2 EMM.
Now, i want to download the emm-agent-android app.
I accessed from my adroid device to my_url:9443/emm -> Device management and i clicked on "Enroll a device" button.
I got this follewed url : my_url:9443/emm/api/device_enroll that i accessed from may device and i clicked on "Download Agent" button.
I got be then redirected to the url: http://my_url:9763/emm/client_app/emm-agent-android.apk web page not found
So I change the url to https://my_url:9443/emm/client_app/emm-agent-android.apk
The download starts but with failure what is the problem?
I assume you have logged to the EMM console using admin / tenant admin credentials for at-least once. If the everything works fine the address to download the agent should be something like "http://10.100.5.37:9763/emm/client_app/emm-agent-android.apk". Make sure you have the client app in "/repository/deployment/server/jaggeryapps/emm/client_app" folder. Try to invoke the download agent address directly from the browser without going through "https://my_url:9443/emm/api/device_enroll". You can not download the agent from "https" endpoint unless the SSL setup is configured properly.
I have checked that the emm-agent-android.apk is in "/repository/deployment/server/jaggeryapps/emm/client_app" but the url "http://my_ip:9763/emm/client_app/emm-agent-android.apk" not found
So I checked listening ports netstat | grep 9443 show lines but nestat|grep 9763 display nothing Is there config file to edit?
Is your Device and the Server in the same network? (Unless your server is hosted in a proper host and it has a public IP which you can access from anywhere)
Related
I have WSO2 IS 5.11 installed on a server under https://server1.wso2.com.
When Im trying to reach new console app Im getting redirected to:
https://localhost:9443/oauth2/token/.well-known/openid-configuration
and then to authorize endpoint:
https://localhost:9443/oauth2/authorize?response_type=code&client_id=CONSOLE&scope=SYSTEM%20openid&redirect_uri=https://server1.wso2.com/console/login&response_mode=query&code_challenge_method=S256&code_challenge=sa3xryaGoX1IoyxZJfoIrE3tAJPUjep30j6izcDtOtc
Why Im getting redirected to localhost:9443? I checked my configuration and there is no localhost in resident IdP.
This can happen due to the server configurations set on WSO2IS, to change that go to <IS-HOME>/repository/conf directory and open deployment.toml configuration file and change the
[server]
hostname = "https://server1.wso2.com"
Also, you can check load balancer configurations/ port mapping and opening ports from the server configurations from the server that you use.
I am doing a POC with my team as we are introducing WSO2 components and am working with the API Manager 3.0.
I seem to be having issues loading the WSO2 API Manager / API Publisher on the defined URL;
https://[ip address]/publisher
The page is not loading and I keep getting a spinning circle.
Steps I have taken:
Stop API Manager at command prompt with [Ctrl + C] command
Modified deployment.toml file specified paths for the localhost to our IP Address, API [publisher, gateway and store] URL values to use our IP Address as well.
Changed carbon.xml and api_manager.xml
Start API Manager with wso2server.bat --run command
Issues are as follows;
api_manager.xml values are reset to localhost and not the IP Address I modified it to.
The API Publisher page is not loading and I am not able to get to the API Publisher login page.
I am an administrator on the Windows Server hosting this, so all changes are made as admin.
First of all, APIM 3.0 has a new config model, where all configurations are available (only) in deployment.toml. All other configurations are populated based on that, and shouldn't be changed manually.
Second, you don't need to replace all occurrences of localhost to IP as many are local calls.
Third, the correct URL should have the port, unless you have a reverse proxy in front of API.
eg. https://[ip address]:9443/publisher
Sounds good and thanks for the input. I will give this a try and post back to the thread.
I am using the IP and Port for now with no reverse proxy but plan to add one, once I can get through this part.
Much appreciated.
I have a test server that I can ping successfully although I'm not able to see a hello world test page I've created and mapped in IIS. I've also created an Inbound rule in the windows firewall. Is there something else I'm missing? I'm browsing http://x.x.x.x:888
Any advice greatly appreciated.
Many thanks,
Update
This is a AWS server
Have tried telnet from a client machine but I get Operation timed out
Nothing in IIS logs (C:\inetpub\logs\LogFiles\xxx)
Port 888 is what I assign the test website to in IIS
Have also moved the test file (index.htm) into the default website within IIS and tried browsing http://x.x.x.x:80/index.htm but I get This site can’t be reached
browsing http://localhost on the server displays the 'hello' message test page.
In windows explorer I've gone to the security settings by right clicking on the website folder and allowing 'everyone' read access
Firewall screen shot
Important update
the IP http://x.x.x.x:888 is the public IP within AWS for the server, not the interal IP of that actual server
On windows 10, I found a firewall issue for my testing server, this worked for me: go to Windows Firewall -> Advanced Settings -> Windows Firewall properties and set a public profile to allow incoming connections.
I am executing sample programm of wso2. I have installed wso2is on different machine and tomcat is on local machine. I have changed localhost:9443 to my ipaddress(eg 192.168.1.xxx) from travelocity.properties and avi.properties. But when I execute sample from click on login button it always redirecting me localhost and giving error.
I think you need to try the following,
While the tomcat is running,
Open the travelocity.war with an archive manager
Edit the travelocity.properties file,
update SAML2.IdPURL value
eg : SAML2.IdPURL=https://192.168.1.7:9443/samlsso
Save and update the travelocity.com web app
Restart the tomcat server just to be sure (You don't really have to do this since tomcat hot deploys once it detects a change)
I tried this locally and it redirected me to the IP address I put in SAML2.IdpURL. Clearly the problem seems to be a configuration error on the travelocity.com web app side :)
You need to change <HostName> and <MgtHostName> attributes at repository/conf/carbon.xml of your Identity Server with your IP address. By default they are set as localhost, so when logging it will be redirected to location specified there.
I'm playing with travelocity sample application, but I'm having a problem:
when I access the application at 10.0.3.124:8080/travelocity.com I end up at https://localhost:9444/commonauth?SAMLRequest=... even though I configured the "host" parameter in carbon.xml. I've also searched for localhost in authenticators.xml and application-authentication.xml and found IdentityProviderSSOServiceURL that i changed from localhost to machine ip.
I'm on a laptop and my application server and IS istances run on a different machine with the 10.0.3.124 IP.
I successfully access the IS admin console.
Where's the problem?
It seems that I also had to configure the <MgtHostName>10.0.3.124</MgtHostName> in carbon.xml.
Thanks
There is a file named identity.xml in side IS_HOME/repository/conf which carries following configuration.
<SSOService>
<IdentityProviderURL>https://localhost:9443/samlsso</IdentityProviderURL>
Please configuring this with your environment parameters.
Thanks,
Pushpalanka