I can not understand how to modify WSO2 with its own IP address and no longer have localhost.
Can someone explain?
Thank you for your help.
Tof
You can edit the carbon.xml file in wso2iot-3.0.0/core/repository/conf location and change the following tags with the IP Address.
<HostName>192.168.10.1</HostName>
<MgtHostName>192.168.10.1</MgtHostName>
Restart the server to apply the changes.
WSO2 IoT 3.1.0 is released now, and we have included a script to change the localhost URL to an IP. Please check in the [WSO2 IoT-3.1.0]/scripts/change-ip.sh. When you run this, it will configure the server to use the IP instead of the localhost.
Try changing below configurations
1) comment Hostname and MgtHostName Field in carbon.xml
2) replace all the localhost with IP in sso-idp-config.xml
3) core/repository/deployment/server/jaggeryapps/devicemgt/app/conf/app-conf.json
"identityProviderUrl" : "https://IP:9443/samlsso",
"acs": "https://IP:9443/devicemgt/uuf/sso/acs",
4) core/repository/deployment/server/jaggeryapps/api-store/site/conf/site.json
"identityProviderURL" : "https://IP:9443/samlsso",
5) core/repository/conf/app-manager.xml
Under SSO-configuration set "identityProviderURL" : "https://IP:9443/samlsso"
Complete list at docs.wso2.com/display/IoTS300/Configuring+WSO2+IoT+Server+with+the+IP
https://docs.wso2.com/display/IoTS300/Configuring+WSO2+IoT+Server+with+the+IP
Related
WSDL 1.1 & WSDL 2.0 are not opening in the management console when I open the WSDL in the management console it shows This site can’t be reached error I don't know why this happening. So please help me to sort this out.
Note: No error throws in both carbon and wire logs
Thanks!
you have misconfiguration problem i think. becouse you have wso2 in AWS and this ip-10-50-11-169... is not a hostname or your ip adress.
Can you check your /etc/hosts on server? maybe you must change fqdn in aws account
or you can check wso2 hostname/ip adress configuration in axis2.xml <parameter name="WSDLEPRPrefix"..
You need to add the following property to your axis2.xml to pick the correct FQDN/Hostname when generating WSDL URLs. So add the Hostname you are using to access the services here or if you are using the same hostname used for management console add the hostname with the correct service port.(8280 or 8343)
<parameter name="WSDLEPRPrefix" locked="false">http://ei.wso2.com:80</parameter>
Refer to instructions here.
Also, make sure the FQDN is resolvable and your security groups are allowing access to relevant ports.
· Changing the hostnames from localhost to IP / Domain is not working. Running the API manager server overrides the configuration files (carbon.xml and api-manager.xml) to previous configuration. How should we change the domain names from localhost to domain or live IPs?
· The configuration is not editable in https://localhost:9443/carbon. Is there any other way to change configuration? Even the configuration is not visible in https://localhost:9443/admin.?
Please help...
I guess you are referring to APIM 3.0.0 which comes with new configuration model. These configs are need to be modified in the deployment.toml file. Please refer https://apim.docs.wso2.com/en/latest/Reference/ConfigCatalog/ for more information.
See details on changing hostname in https://apim.docs.wso2.com/en/latest/InstallAndSetup/DeployingWSO2APIManager/changing-the-hostname/
I followed this link for configuring multiple hostnames for my identity server. Things are working fine and as expected for all samlsso based usecases.
Please note that the actual hostname and management hostname paramter in the carbon.xml is different from the virtual hostname that i give in the apache front end. (Since there are multiple host names)
However when a passivests request comes through one of the virtual hosts it is received by the wso2 identity server with the virtual host and when the redirection happens to the commonauth url the hostname changes to the one which is defined in the carbon.xml file. so finally when the login page comes up it will be in the format of
Using protocol in lieu of https as I don't have enough reputation to post more than 2 links. :P
protocol://managementhostname/authenticationendpoint/login.do?commonAuthCallerPath=%2Fpassivests&forceAuth=false&passiveAuth=false&tenantDomain=domain1&wa=wsignin1.0
it should have been
protocol://virutalhostname/authenticationendpoint/login.do?commonAuthCallerPath=%2Fpassivests&forceAuth=false&passiveAuth=false&tenantDomain=domain1&wa=wsignin1.0
for requests to the /samlsso endpoint it is happening properly with virtualhostname.
It would be great if somebody can throw some light on the issue.
Thanks in advance
I'm using WSO2 identity server (on port 9443) and enterprise service bus (ESB, on port 9444). I configured ESB to use IS SSO. But everytime I try to login into ESB it redirects me to IS and there it redirects me to URL localhost:9443/samlsso.
I already tried changing this URL in identities.xml and carbon.xml without access.
Where can I configure the redirection address?
In carbon.xml I specified the hostname as "HostName" and "MgtHostName". But IS still uses localhost.
Thanks!
WSO2 has a script located at:
<IOTS_HOME>/scripts
run
./change-ip.sh
Tip: The script will find and replace the IP address given in argument1 (localhost) with the IP address given as argument2 (10.10.10.14), in the necessary configuration files.
Check Docs to configure Hostname
SSO configuration should in /repository/conf/security/authenticators.xml as follows to change the hostname of redirection url of Identity Server,
<Authenticator name="SAML2SSOAuthenticator" disabled="false">
<Priority>1</Priority>
<Config>
<Parameter name="LoginPage">/carbon/admin/login.jsp</Parameter>
<Parameter name="ServiceProviderID">carbonServer</Parameter>
<Parameter name="IdentityProviderSSOServiceURL">https://<HostNameOfIdentitiyServer>:9443/samlsso</Parameter>
<Parameter name="NameIDPolicyFormat">urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified</Parameter>
<Parameter name="AssertionConsumerServiceURL">https://<HostNameOfIdentitiyServer>:9443/acs</Parameter>
</Config>
Ok, I found a solution.
I did a search+replace over all XML documents inside the IS and ESB package and replaced all "localhost" by my hostname.
In the identity.xml there's a SSOService/IdentityProviderURL tag, that one seems important for SAML authentication.
carbon.xml file under /repository/conf folder.
Change <HostName>localhost</HostName> to your IP.
<HostName>x.x.x.x</HostName>
Add the URL of your VM in system32/drivers/etc/hosts and map it to localhost.
Change the hosts file and map localhost to Ip-address of your VM where WSO2 is running.
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