Re: [Dev] Returning token state from Identity Server introspect response.

Hi Ishara, According to the specification, it is not recommended to expose too much details about why the token is not active. Note that to avoid disclosing too much of the authorization server's state to a third party, the authorization server SHOULD NOT include any additional

Re: [Dev] Returning token state from Identity Server introspect response.

Hi Ishara, The '*active*' parameter is mandatory according to the Introspection spec[1], to indicate the status of the token. If we are to send something like what you have suggested we could do so by using a custom attribute in response. But then again that would be something specific to our

[Dev] Returning token state from Identity Server introspect response.

I have used introspect end point to get token info with Identity Server 5.3.0 I get {'active':false} response even for expired token. *Request :* curl -k -H 'Content-Type: application/x-www-form-urlencoded' -X POST --data 'token=a2c12c81-33fb-3e07-aa5e-c50639011199'

Re: [Dev] 401 Error: Unauthorized - Illegal access attempt from IP address 10.100.0.187 while trying to authenticate access to service ExternalTryitService

Hi, I am facing the same issue with the KeyManager from API Manager. Did you find out what was the problem? Thanks! -- View this message in context:

Re: [Dev] javax.naming.NameNotFoundException Name [jdbc/WSO2CarbonDB] is not bound in this Context

Looking up jdbc/WSO2CarbonDB as it is does not work. All the datasources are registered under the JNDI context java:comp/env. So, if your jndi key is jdbc/WSO2CarbonDB, then it can be found at java:comp/env /jdbc/WSO2Ca rbonDB. This ambiguity is coming from JNDI itself. See [1] for a detailed

Re: [Dev] javax.naming.NameNotFoundException Name [jdbc/WSO2CarbonDB] is not bound in this Context

Thanks to Manuri. I will have a try later and update here. On Fri, Dec 2, 2016 at 1:25 PM, Manuri Amaya Perera wrote: > Hi Wenxing, > > Did you try prepending "java:comp/env/" to your JNDI name where you use > it inside the webapp. (eg: java:comp/env/jdbc/WSO2CarbonDB). > >

Re: [Dev] Fixed an issue in Swagger-parser

PR Merged. @Maheshika, could you please release the bundle? Thanks Thusitha On Thu, Dec 1, 2016 at 5:40 PM, Ishara Cooray wrote: > Hi Thusitha, > > Please find the updated PR https://github.com/wso2/orbit/pull/250 > > Thanks & Regards, > Ishara Cooray > Senior Software

Re: [Dev] carbon-mediation-4.6.8 Staged

Hi Nuwan, carbon-mediation 4.6.8 is released now. Regards Senduran On Fri, Dec 2, 2016 at 11:57 AM, Nuwan Wimalasekara wrote: > Hi Senduran > > Can you please release the carbon-mediation 4.6.8 > > Thanks, > Nuwanw > > On Thu, Dec 1, 2016 at 10:56 AM, Thilini Shanika

Re: [Dev] Fixed an issue in Swagger-parser

Hi Thusitha Successfully deployed. On Fri, Dec 2, 2016 at 9:33 AM, Thusitha Thilina Dayaratne < thusit...@wso2.com> wrote: > PR Merged. > > @Maheshika, could you please release the bundle? > > Thanks > Thusitha > > > On Thu, Dec 1, 2016 at 5:40 PM, Ishara Cooray wrote: > >>

Re: [Dev] Regarding configuration parameter WSO2 ESB

Hi Amit, If you are using you can use multiple registry or local entry projects for different environments. [1] https://docs.wso2.com/display/DVS380/Creating+Governance+Registry+Artifacts [2] https://docs.wso2.com/display/ESB500/Working+with+Local+Registry+Entries On Thu, Dec 1, 2016 at 6:32