[Dev] Changing levels of APIs didn't help

Hi All, I'm having three APIs(PizzaShackAPI, MyAPI, NewAPI) in my set up and when i navigate to configure>>logging under "Configure Log4J Loggers" section in carbon management console of APIM, i can see the below loggers at level "ERROR". I suspect by using this we can view the per API

Re: [Dev] Deprecating Mepin Authenticator

Hi Omindu, We have tried to use the new MePIN endpoint for API version 4 . But we got error from Mepin back end as {"status":"error","status_text":"Service plan does not permit requested action. Please contact supp...@meontrust.com"}. Seems we need a commercial account for the Mepin API access.

Re: [Dev] Showing a custom URL for the API in the store

Yes, Eshara. This is for tenants. I'm looking for a way to do the same for the super tenant. On Tue, Jul 24, 2018 at 11:16 PM Ishara Cooray wrote: > Hi Shazni, > > Hope you are referring to this [1]. But this is for tenants. > > [1] >

Re: [Dev] Showing a custom URL for the API in the store

Hi Shazni, Hope you are referring to this [1]. But this is for tenants. [1] https://docs.wso2.com/display/AM220/Customize+the+API+Store+and+Gateway+URLs+for+Tenants Thanks & Regards, Ishara Cooray Senior Software Engineer Mobile : +9477 262 9512 WSO2, Inc. | http://wso2.com/ Lean . Enterprise .

[Dev] Showing a custom URL for the API in the store

Is there a configuration that I can use to customize the endpoint URLs that are displayed in the API store? Currently, the URL is showing up with the prefix of whatever I have configured in the GatewayEndpoint in the api-manager.xml. Is there a way to override it without changing the

Re: [Dev] How to check whether an SP node is in Active or Passive state

Hi Fazlan, You can use following . [1] https://github.com/wso2/carbon-analytics/blob/master/components/org.wso2.carbon.stream.processor.statistics/src/main/java/org/wso2/carbon/stream/processor/statistics/internal/service/NodeConfigServiceComponent.java Regards, Damith On Tue, Jul 24, 2018 at

Re: [Dev] How to check whether an SP node is in Active or Passive state

Also, there are CLI logs where it’s print the status of the node. Please refer the doc[2] [2017-10-23 08:56:57,380] INFO {org.wso2.carbon.stream.processor.core.internal.ServiceComponent} - WSO2 Stream Processor Starting in Two Node Minimum HA Deployment [2017-10-23 08:56:57,392] INFO

Re: [Dev] How to check whether an SP node is in Active or Passive state

I need to check the status within a custom event source running within SP. Is there an OSGI service which I could make use of? On Tue, Jul 24, 2018 at 11:58 PM Damith Wickramasinghe wrote: > Hi fazlan, > > we have apis exposed where you can get the information. > > eg:- curl -k -X GET

Re: [Dev] How to check whether an SP node is in Active or Passive state

Hi fazlan, we have apis exposed where you can get the information. eg:- curl -k -X GET http://localhost:9090/statistics -H "accept: application/json" -u admin:admin -k -v will provide you a json with all the information. see[1] [1]

[Dev] How to check whether an SP node is in Active or Passive state

Hi, How is $subject done in SP? Can you point me to a source location? -- Thanks & Regards, *Fazlan Nazeem* Senior Software Engineer WSO2 Inc Mobile : +94772338839 fazl...@wso2.com ___ Dev mailing list Dev@wso2.org

Re: [Dev] Deprecating Mepin Authenticator

Hi Biruntha, Are there any plans to update the connector with the new APIs ? Thanks, Omindu. On Tue, Jul 24, 2018 at 11:04 AM Biruntha Gnaneswaran wrote: > Hi All, > > We are planning to deprecate Mepin authenticator[1] from the store[2]. In > our Mepin authenticator, we are using the Mepin

Re: [Dev] [APIM 2.5.0 + ISKM 5.6.0 + Micro-GW 2.5.0] JWT issuer value

Hi, I quickly checked the backend JWT scenario and observed the following. 1. is set as follows (in api-manager.xml) https://localhost:8243/revoke 2. The resolved value of "iss" of the backend JWT is, "iss": "wso2.org/products/am" Based on the code, it seems like inbound JWT token is using

Re: [Dev] [APIM 2.5.0 + ISKM 5.6.0 + Micro-GW 2.5.0] JWT issuer value

Yes +1, and shall we change the configured value in identity.xml to gateway token endpoint? Because otherwise, it will use the default ( https://localhost:9443/oauth2/token) and we are exposing the IS token endpoint to outside. And as we have already registered gateway as the issuer in MG configs,

Re: [Dev] [APIM 2.5.0 + ISKM 5.6.0 + Micro-GW 2.5.0] JWT issuer value

So this means that IS already has a special config for that, which also means that we do not have to introduce yet another config and can reuse what IS is already using right? On Mon, Jul 23, 2018 at 11:20 PM Malintha Amarasinghe wrote: > Looks like they are using the "IDTokenIssuerID" from

Re: [Dev] [APIM 2.5.0 + ISKM 5.6.0 + Micro-GW 2.5.0] JWT issuer value

Looks like they are using the "IDTokenIssuerID" from identity.xml. If it is not specified, it uses the token API URL ( https://localhost:9443/oauth2/token). ${carbon.protocol}://${carbon.host}:${carbon.management.port}/oauth2/token [1]

Re: [Dev] IAM: Error while uploading the metadata file in Sp creation.

Updated the new file in IS 5.5.0, 5.6.0, and 5.7.0. https://docs.wso2.com/display/IS560/Configuring+SAML2+Web+Single-Sign-On -- *Samuel Gnaniah* Senior Lead Technical Writer WSO2 (pvt.) Ltd. Colombo, Sri Lanka (+94) 773131798 On Tue, Jul 24, 2018 at 11:14 AM, Samuel Gnaniah wrote: >

Re: [Dev] [APIM 2.5.0 + ISKM 5.6.0 + Micro-GW 2.5.0] JWT issuer value

Do we know how IS generates the "iss" when issuing JWT tokens? We should try to leverage that so that we maintain consistency. Again, by making it backwards compatible too. On Mon, Jul 23, 2018 at 11:01 PM Malintha Amarasinghe wrote: > Hi Nuwan, > > We can use a new config under . If it is not

Re: [Dev] [APIM 2.5.0 + ISKM 5.6.0 + Micro-GW 2.5.0] JWT issuer value

Hi Nuwan, We can use a new config under . If it is not specified, we can use the config from . We can make that config commented out when shipping. Also, the shipped (default) value can be added as the token API URL (The same existing value). From these, existing customers using backend JWT (not