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
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
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:
>
>>
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
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
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:
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'
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
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
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).
>
>
10 matches
Mail list logo