Hi All,
I think REST connector should have single endpoint. The rest call can have
tenant ID in a header or as a request parameter. Then the API gateway(
API-Manager) should be able to distinguish the respective endpoint if
necessary. This is a functionality of APIM.
The reasons are,
1. REST conne
Hi Dilini,
Thanks for the help,It works with a slight change to the *names_2.csv* file
attached in the JIRA[1].As you suggested , I had to add a new column with
the password for the user in between username and claim URL columns.
Sample format of the csv file.
UserName,Password,Claims
> chris,ch
HI all,
Please note $subject,
org.wso2.carbon.deployment
carbon-deployment
4.7.0
--
Best Regards,
Kalpa Welivitigoda
Senior Software Engineer, WSO2 Inc. http://wso2.com
Email: kal...@wso2.com
Mobile: +94776509215
___
Dev mailing list
Dev@wso2.org
ht
Hi Sajith,
We could not keep each and every tenant authentication configuration in
app-manager.xml, due to dynamic nature of tenant creation and the growth.
appmgt.mdm.rest.connector is the default connector that we provided to
connect with WSO2EMM. We could keep it's configurations in the regist
Hi,
We are working on $subject. Anyway after integration, custom runtime
environment feature is broken because TomEE is using different class
loading behaviour. We need to override the class loading behaviour in TomEE
in order to preserve the behaviour of this feature of AS. After a
discussion on
Hi All,
EMM supports multi-tenancy it is designed to work with one instance of App
> Manager via OSGI services. When they work together they function as one
> product, hence EMM and App Manager share same tenants across the multi
> tenanted environment.
>
This means we don't need to keep the tena
Hi Sachith,
Basically you have to overwrite the "
*repository\deployment\server\jaggeryapps\portal\theme\templates\dashboard.jag*"
file by copying it and pasting it under "
*repository\deployment\server\jaggeryapps\portal\extensions\themes\basic\templates\dashboard.jag*".
That's how the DS theme t
On Wed, Jul 6, 2016 at 9:55 AM, Isuru Haththotuwa wrote:
> The rationale behind my previous statement is that once the docker images
> are pushed to a registry, the users do not have to continuously build them,
> but rather can extend from the product Docker images and do development and
> testi
Hi Greg team,
In DS we are pointing to jaggery extensions version 1.5.3-SNAPSHOT and
until 5 th build was success. And now the build is failing with the below
error.
Software being installed: ws Module - Feature 1.5.3.SNAPSHOT
(org.jaggeryjs.modules.ws.feature.group 1.5.3.SNAPSHOT)
Missing requir
Okay thanks
On Thursday, 7 July 2016, Abimaran Kugathasan wrote:
> Hi Vanji,
>
>
> There were some JARs got duplicated, we will fix it in the next release.
>
> On Fri, Jul 8, 2016 at 5:05 AM, Vanjikumaran Sivajothy > wrote:
>
>> Hi folks,
>> I was checking the plugin directory of APIM 2.0 BETA
Hi Venkat,
SSL OFFLOAD thing I can't see https is enabled.
On Wed, Jul 6, 2016 at 10:11 PM, Venkat Raman wrote:
> Hi Isuru,
>
> I'm blocked by this issue from yesterday. We need have a small
> discussion ASAP. I'll try to explain the scenario more clearly here than I
> did in hangouts.
>
> F
Hi Vanji,
There were some JARs got duplicated, we will fix it in the next release.
On Fri, Jul 8, 2016 at 5:05 AM, Vanjikumaran Sivajothy
wrote:
> Hi folks,
> I was checking the plugin directory of APIM 2.0 BETA 2 and notice
> org.wso2.carbon.identity.oauth.stub has two diff versions
>
> org.w
Hi folks,
I was checking the plugin directory of APIM 2.0 BETA 2 and notice
org.wso2.carbon.identity.oauth.stub has two diff versions
org.wso2.carbon.identity.oauth.stub_5.0.8.jar
org.wso2.carbon.identity.oauth.stub_5.1.1.SNAPSHOT.jar
--
Vanjikumaran Sivajothy
*Associate Technical Lead*
*WSO2 In
Hi KasunG,
I have tested the carbon-feature-plugin and the kernel with the new
upgrades and sent two PRs for both repos. But at first, as you said, carbon
feature plugin has to be released in order to move the kernel to Neon
release because neon plugins don't work with the old versions of tycho.
Hi Mentors,
In addition to refining the membership scheme code, I looked into following
features of Azure.
*Azure dynamic load balancing*
Azure has a native load balancer which is very easy to configure. It’s a
layer 4 (TCP, UDP) load balancer which helps to spread traffic among
healthy virtu
Hi Thilini/Abimaran,
I got the rational behind the design. Thank you very much for the
explanations.
On Thu, Jul 7, 2016 at 5:45 PM, Abimaran Kugathasan
wrote:
>
>
> On Thu, Jul 7, 2016 at 5:02 PM, Asanka Vithanage wrote:
>
>> Hi All,
>>
>> Thanks for all the replies.
>>
>> @Roshan
>>
>> We ca
On Thu, Jul 7, 2016 at 5:02 PM, Asanka Vithanage wrote:
> Hi All,
>
> Thanks for all the replies.
>
> @Roshan
>
> We can't remove subscriptions by going to the Application, Application
> only lists logged in users subscriptions.
>
> @Lakshman/Bhathiya/Chamin
>
> Yes, I understand we can achieve d
Hi,
AFAIU the proper way of deleting an API is first removing from the store
(avoiding creating further subscriptions) by changing its lifecycle status
to "Deprecated" as mentioned by Chamin and then removing the API from the
Gateway by retiring it (avoiding further invocations).
Otherwise applica
Thanks Jerad and Prabushi.
@Jerad: What do you mean by extending the dashboard.jag?
Regards,
Sachith
On Thu, Jul 7, 2016 at 12:07 AM, Prabushi Samarakoon
wrote:
> Hi Sachith,
>
> Currently, we don't allow to change the dashboard logo. But, you can
> easily change the dashboard title which loca
Hi All,
Thanks for all the replies.
@Roshan
We can't remove subscriptions by going to the Application, Application only
lists logged in users subscriptions.
@Lakshman/Bhathiya/Chamin
Yes, I understand we can achieve delete API following these steps. But
those are actually workarounds.
Why don
Hi,
Change the lifecycle to "Block"
Then existing users (already who subscribed) cannot use the API, also new
users are not able to subscribe to the blocked API.
In this state also, you are not allowed to delete the API form the API
publisher since there is a subscriber.
If you want to delete the
On Thu, Jul 7, 2016 at 3:43 PM, Asanka Vithanage wrote:
> Hi All,
>
> Using API Publisher and Store, I am trying to achieve the $Subject. But it
> seems via current store and publisher UIs, we can't do that.
>
> Let's think we create two users called userPub and userSub with only login
> and Mana
Go to Application section and then subscription tab then unsubscribe.
On Thu, Jul 7, 2016 at 3:58 PM, Lakshman Udayakantha
wrote:
> Hi Asanka,
>
> AFAIR we can't delete an API which has subscriptions rather you can block
> the API using API publisher.
>
> Thanks
>
> On Thu, Jul 7, 2016 at 3:45 P
Hi Asanka,
AFAIR we can't delete an API which has subscriptions rather you can block
the API using API publisher.
Thanks
On Thu, Jul 7, 2016 at 3:45 PM, Asanka Vithanage wrote:
> Hi,
>
> Sorry. Topic should be changed as [APIM 200] How API publisher can delete
> a API which has subscriptions
>
Hi,
Sorry. Topic should be changed as [APIM 200] How API publisher can delete a
API which has subscriptions
On Thu, Jul 7, 2016 at 3:43 PM, Asanka Vithanage wrote:
> Hi All,
>
> Using API Publisher and Store, I am trying to achieve the $Subject. But it
> seems via current store and publisher UI
Hi John,
You can try using VFS Transport [1] to achieve your requirement.
[1] https://docs.wso2.com/display/ESB490/VFS+Transport
Regards,
Malith
On Tue, Jul 5, 2016 at 8:12 PM, John Q wrote:
> Hello folks,
> can any body tell me hot to upload a file from a sequence in the ESB? I
> mean, there
Hi All,
Using API Publisher and Store, I am trying to achieve the $Subject. But it
seems via current store and publisher UIs, we can't do that.
Let's think we create two users called userPub and userSub with only login
and Manage permissions.
Then "userPub" login to the API Publisher and create/P
Great
Suho
On Thu, Jul 7, 2016 at 2:48 PM, Supun Sethunga wrote:
> Hi,
>
> Thanks Suho for the quick fix. I tested with the latest siddhi (with 50+
> million events, spanning over 1.5 hours ), in both single node and minimum
> HA setups, and the issue no longer exists.
>
> Thanks,
> Supun
>
> O
Hi,
We cant use id token that we get from IS 5.1.0 since we can't configure Aud
there but this should be fixed in IS 5.2.0.
And I used sample jwt generator class to build a JWT and test the scenario.
Thanks,
Ishara
On Wed, Jul 6, 2016 at 11:58 PM, Malaka Silva wrote:
> +Keerthika
>
> On Wed,
Hi,
Thanks Suho for the quick fix. I tested with the latest siddhi (with 50+
million events, spanning over 1.5 hours ), in both single node and minimum
HA setups, and the issue no longer exists.
Thanks,
Supun
On Mon, Jul 4, 2016 at 12:31 PM, Supun Sethunga wrote:
> Execution plan:
>
> [1]
> ht
30 matches
Mail list logo