After configuring the Email as Username feature with the externalized gateway deployment and when publishing APIs to the externalized gateway, the artifact is not getting deployed, and hence, able to see the 404 response when invoking the API.
Steps to reproduce:
Configure the deployment with an external gateway (profiled) with an All in One instance. (Please add the [apim.event_hub] configurations)
Configured the Email as Username feature by referring to the documentation[1].
Start all the nodes. (When starting the profiled gateway, not able to see the artifact deployment logs)
[2022-03-23 13:41:52,229] INFO - QpidServiceComponent Activating Andes Message Broker Engine...
[Broker] BRK-1001 : Startup : Version: 0.11 Build: 90784:90849
[Broker] MNG-1001 : Startup
[Broker] MNG-1004 : Ready : Using the platform JMX Agent
[Broker] BRK-1002 : Starting : Listening on TCP port 5673
[2022-03-23 13:41:52,706] INFO - listening [Broker] BRK-1002 : Starting : Listening on TCP port 5673
[Broker] BRK-1002 : Starting : Listening on TCP/SSL port 8673
[2022-03-23 13:41:52,711] INFO - listening [Broker] BRK-1002 : Starting : Listening on TCP/SSL port 8673
[Broker] BRK-1004 : Qpid Broker Ready
[2022-03-23 13:41:52,716] INFO - QpidServiceComponent AMQP Host Address : 0.0.0.0 Port : 5673
[2022-03-23 13:41:52,717] INFO - QpidServiceComponent Successfully connected to AMQP server on port 5673
[2022-03-23 13:41:52,718] INFO - QpidServiceComponent WSO2 Message Broker is started.
[2022-03-23 13:41:52,750] INFO - JMSConnectionFactory JMS ConnectionFactory : Siddhi-JMS-Consumer initialized
[2022-03-23 13:41:52,761] INFO - JMSConnectionFactory JMS ConnectionFactory : Siddhi-JMS-Consumer initialized
[2022-03-23 13:41:52,771] INFO - JMSConnectionFactory JMS ConnectionFactory : Siddhi-JMS-Consumer initialized
[2022-03-23 13:41:52,789] INFO - JMSConnectionFactory JMS ConnectionFactory : Siddhi-JMS-Consumer initialized
[2022-03-23 13:41:52,798] INFO - JMSConnectionFactory JMS ConnectionFactory : Siddhi-JMS-Consumer initialized
[2022-03-23 13:41:52,814] INFO - JMSConnectionFactory JMS ConnectionFactory : Siddhi-JMS-Consumer initialized
[2022-03-23 13:41:52,824] INFO - JMSConnectionFactory JMS ConnectionFactory : Siddhi-JMS-Consumer initialized
[2022-03-23 13:41:52,839] INFO - JMSConnectionFactory JMS ConnectionFactory : Siddhi-JMS-Consumer initialized
[2022-03-23 13:41:52,851] INFO - JMSConnectionFactory JMS ConnectionFactory : Siddhi-JMS-Consumer initialized
[2022-03-23 13:41:53,095] INFO - JMSConnectionFactory JMS ConnectionFactory : Siddhi-JMS-Consumer initialized
[2022-03-23 13:41:53,117] INFO - PassThroughHttpListener Starting Pass-through HTTP Listener...
[2022-03-23 13:41:53,122] INFO - PassThroughListeningIOReactorManager Pass-through HTTP Listener started on 0.0.0.0:8281
[2022-03-23 13:41:53,123] INFO - PassThroughHttpMultiSSLListener Starting Pass-through HTTPS Listener...
[2022-03-23 13:41:53,132] INFO - PassThroughListeningIOReactorManager Pass-through HTTPS Listener started on 0.0.0.0:8244
[2022-03-23 13:41:53,195] WARN - SSLUtilBase The trusted certificate with alias [thawtepremiumserverca] and DN [EMAILADDRESS=premium-server@thawte.com, CN=Thawte Premium Server CA, OU=Certification Services Division, O=Thawte Consulting cc, L=Cape Town, ST=Western Cape, C=ZA] is not valid due to [NotAfter: Sat Jan 02 05:29:59 IST 2021]. Certificates signed by this trusted certificate WILL be accepted
[2022-03-23 13:41:53,196] WARN - SSLUtilBase The trusted certificate with alias [identrustdstx3] and DN [CN=DST Root CA X3, O=Digital Signature Trust Co.] is not valid due to [NotAfter: Thu Sep 30 19:31:15 IST 2021]. Certificates signed by this trusted certificate WILL be accepted
[2022-03-23 13:41:53,197] WARN - SSLUtilBase The trusted certificate with alias [addtrustclass1ca] and DN [CN=AddTrust Class 1 CA Root, OU=AddTrust TTP Network, O=AddTrust AB, C=SE] is not valid due to [NotAfter: Sat May 30 16:08:31 IST 2020]. Certificates signed by this trusted certificate WILL be accepted
[2022-03-23 13:41:53,198] WARN - SSLUtilBase The trusted certificate with alias [wso2carbon] and DN [CN=localhost, OU=WSO2, O=WSO2, L=Mountain View, ST=CA, C=US] is not valid due to [NotAfter: Tue Jan 25 13:00:43 IST 2022]. Certificates signed by this trusted certificate WILL be accepted
[2022-03-23 13:41:53,198] WARN - SSLUtilBase The trusted certificate with alias [mzyxmmfkogywmwi0zwnmndcxngywymm4zta3mwi2ndazzgqzngm0zgrlnjjkodfkzdriotfkmwfhmzu2zgvlng_rs256] and DN [CN=localhost, OU=WSO2, O=WSO2, L=Mountain View, ST=CA, C=US] is not valid due to [NotAfter: Tue Jan 25 13:00:43 IST 2022]. Certificates signed by this trusted certificate WILL be accepted
[2022-03-23 13:41:53,198] WARN - SSLUtilBase The trusted certificate with alias [gateway_certificate_alias] and DN [CN=localhost, OU=WSO2, O=WSO2, L=Mountain View, ST=CA, C=US] is not valid due to [NotAfter: Tue Jan 25 13:00:43 IST 2022]. Certificates signed by this trusted certificate WILL be accepted
[2022-03-23 13:41:53,199] WARN - SSLUtilBase The trusted certificate with alias [globalsignr2ca] and DN [CN=GlobalSign, O=GlobalSign, OU=GlobalSign Root CA - R2] is not valid due to [NotAfter: Wed Dec 15 13:30:00 IST 2021]. Certificates signed by this trusted certificate WILL be accepted
[2022-03-23 13:41:53,199] WARN - SSLUtilBase The trusted certificate with alias [soneraclass2ca] and DN [CN=Sonera Class2 CA, O=Sonera, C=FI] is not valid due to [NotAfter: Tue Apr 06 12:59:40 IST 2021]. Certificates signed by this trusted certificate WILL be accepted
[2022-03-23 13:41:53,199] WARN - SSLUtilBase The trusted certificate with alias [verisigntsaca] and DN [CN=Thawte Timestamping CA, OU=Thawte Certification, O=Thawte, L=Durbanville, ST=Western Cape, C=ZA] is not valid due to [NotAfter: Sat Jan 02 05:29:59 IST 2021]. Certificates signed by this trusted certificate WILL be accepted
[2022-03-23 13:41:53,200] WARN - SSLUtilBase The trusted certificate with alias [quovadisrootca] and DN [CN=QuoVadis Root Certification Authority, OU=Root Certification Authority, O=QuoVadis Limited, C=BM] is not valid due to [NotAfter: Thu Mar 18 00:03:33 IST 2021]. Certificates signed by this trusted certificate WILL be accepted
[2022-03-23 13:41:53,200] WARN - SSLUtilBase The trusted certificate with alias [addtrustqualifiedca] and DN [CN=AddTrust Qualified CA Root, OU=AddTrust TTP Network, O=AddTrust AB, C=SE] is not valid due to [NotAfter: Sat May 30 16:14:50 IST 2020]. Certificates signed by this trusted certificate WILL be accepted
[2022-03-23 13:41:53,201] WARN - SSLUtilBase The trusted certificate with alias [keynectisrootca] and DN [CN=KEYNECTIS ROOT CA, OU=ROOT, O=KEYNECTIS, C=FR] is not valid due to [NotAfter: Tue May 26 05:30:00 IST 2020]. Certificates signed by this trusted certificate WILL be accepted
[2022-03-23 13:41:53,201] WARN - SSLUtilBase The trusted certificate with alias [addtrustexternalca] and DN [CN=AddTrust External CA Root, OU=AddTrust External TTP Network, O=AddTrust AB, C=SE] is not valid due to [NotAfter: Sat May 30 16:18:38 IST 2020]. Certificates signed by this trusted certificate WILL be accepted
[2022-03-23 13:41:53,201] WARN - SSLUtilBase The trusted certificate with alias [luxtrustglobalrootca] and DN [CN=LuxTrust Global Root, O=LuxTrust s.a., C=LU] is not valid due to [NotAfter: Wed Mar 17 15:21:37 IST 2021]. Certificates signed by this trusted certificate WILL be accepted
[2022-03-23 13:41:53,330] INFO - TaskServiceImpl Task service starting in STANDALONE mode...
[2022-03-23 13:41:53,387] INFO - RegistryEventingServiceComponent Successfully Initialized Eventing on Registry
[2022-03-23 13:41:53,453] INFO - JMSConnectionFactory JMS ConnectionFactory : Siddhi-JMS-Consumer initialized
[2022-03-23 13:41:53,532] INFO - JMXServerManager JMX Service URL : service:jmx:rmi://localhost:11112/jndi/rmi://localhost:10000/jmxrmi
[2022-03-23 13:41:53,594] INFO - StartupFinalizerServiceComponent Server : WSO2 API Manager-4.0.0
[2022-03-23 13:41:53,595] INFO - StartupFinalizerServiceComponent WSO2 Carbon started in 29 sec
[2022-03-23 13:41:53,603] INFO - JMSConnectionFactory JMS ConnectionFactory : Siddhi-JMS-Consumer initialized
[2022-03-23 13:41:53,636] INFO - JMSConnectionFactory JMS ConnectionFactory : Siddhi-JMS-Consumer initialized
[2022-03-23 13:41:53,654] INFO - JMSConnectionFactory JMS ConnectionFactory : Siddhi-JMS-Consumer initialized
[2022-03-23 13:41:53,673] INFO - JMSConnectionFactory JMS ConnectionFactory : Siddhi-JMS-Consumer initialized
[2022-03-23 13:41:53,691] INFO - JMSConnectionFactory JMS ConnectionFactory : Siddhi-JMS-Consumer initialized
[2022-03-23 13:41:53,748] INFO - JMSConnectionFactory JMS ConnectionFactory : Siddhi-JMS-Consumer initialized
[2022-03-23 13:41:54,276] INFO - JMSConnectionFactory JMS ConnectionFactory : Siddhi-JMS-Consumer initialized
[2022-03-23 13:41:54,291] INFO - JMSConnectionFactory JMS ConnectionFactory : Siddhi-JMS-Consumer initialized
[2022-03-23 13:41:54,309] INFO - JMSConnectionFactory JMS ConnectionFactory : Siddhi-JMS-Consumer initialized
[2022-03-23 13:41:54,354] INFO - CarbonUIServiceComponent Mgt Console URL : https://172.17.0.1:9444/carbon/
[2022-03-23 13:41:54,354] INFO - CarbonUIServiceComponent API Developer Portal Default Context : https://172.17.0.1:9444/devportal
[2022-03-23 13:41:54,355] INFO - CarbonUIServiceComponent API Publisher Default Context : https://172.17.0.1:9444/publisher
[2022-03-23 13:41:54,370] INFO - JMSConnectionFactory JMS ConnectionFactory : Siddhi-JMS-Consumer initialized
[2022-03-23 13:41:54,383] INFO - JMSConnectionFactory JMS ConnectionFactory : Siddhi-JMS-Consumer initialized
[2022-03-23 13:41:54,406] INFO - JMSConnectionFactory JMS ConnectionFactory : Siddhi-JMS-Consumer initialized
[2022-03-23 13:41:54,427] INFO - JMSConnectionFactory JMS ConnectionFactory : Siddhi-JMS-Consumer initialized
[2022-03-23 13:41:54,453] INFO - JMSConnectionFactory JMS ConnectionFactory : Siddhi-JMS-Consumer initialized
[2022-03-23 13:41:54,469] INFO - JMSConnectionFactory JMS ConnectionFactory : Siddhi-JMS-Consumer initialized
[2022-03-23 13:41:55,733] INFO - CallHomeExecutor
....................................................................
wso2am-4.0.0.86 is the latest update level available for the product
wso2am-4.0.0
....................................................................
Go to the publisher portal and publish an API. (Select the Externalized gateway)
Try to invoke the API and be able to see the 404 response.
Description:
After configuring the Email as Username feature with the externalized gateway deployment and when publishing APIs to the externalized gateway, the artifact is not getting deployed, and hence, able to see the 404 response when invoking the API.
Steps to reproduce:
Configured the Email as Username feature by referring to the documentation[1].
Start all the nodes. (When starting the profiled gateway, not able to see the artifact deployment logs)
Go to the publisher portal and publish an API. (Select the Externalized gateway)
Try to invoke the API and be able to see the 404 response.
[1] https://apim.docs.wso2.com/en/latest/install-and-setup/setup/security/logins-and-passwords/maintaining-logins-and-passwords/#setup-an-e-mail-login
Affected Product Version:
4.0.0