Re: [Dev] [UUF] Renaming artifact IDs and directory names of foundation component and default theme

Hi all, With the above mentioned changes, we have released the uuf commons repo[1] 1.0.0-m2. Please make sure that your UUF apps, components, themes follows the naming conventions. [1] https://github.com/wso2/carbon-uuf-common/releases/tag/v1.0.0-m2 Thanks, Shan. On Fri, Jan 13, 2017 at 12:47

Re: [Dev] Show images persisted in a database or in a non-public folder from a uuf app

Hi Nisala, How can we secure this API? Do we have to write a MSF4J Interceptor for that? We can certainly write on, but we are not sure how to access the UUF session to validate the user. So, how can we verify whether the current session is authorized or not. Thanks, KasunG On Fri, Jan 13,

Re: [Dev] STS Client sample Doesn't work for Non-repudiation

Hi, I also tried the STS client with non-repudiation. But gives the following error. Is there any configs need to be changed in the sample? org.apache.rahas.TrustException: Error in obtaining token from : " https://localhost:9443/services/wso2carbon-sts; at

Re: [Dev] [APIM][C5] Intermittent error while loading Swagger Definition

Hi Thusitha, Could you please fix this issue asap , As we got this issue very frequent while doing implementation on C5 work. On Wed, Jan 11, 2017 at 10:12 AM, Thilini Shanika wrote: > Please find the issue in [1] > > [1] https://github.com/wso2/msf4j/issues/337 > > Thanks >

Re: [Dev] Ldap UserStore Configuration: Use of Auxiliary Object Classes

Hello Chamalee, Thank you for the article reference, I have done quite the same setup using OpenLdap instead of ApacheDS. But my question was more on the WSO2 IS side, I don't know if I'm missing something but, using an LDAP UserStore, I failed to find in the console management a place to

Re: [Dev] STS Client sample Doesn't work for Non-repudiation

Hi Ashen, Few things you need to pay attention while getting this client working. 1) As [1] suggests you need to generate a new key pair in client's key store for user. The existing keys in the sample are expired. Therefore please use a new key store and add a new key pair in order to get this

[Dev] Merging multiple Jacoco coverages together

Hi Dharshana, To get a proper understanding of the actual coverage, merging of all the jacoco coverages is a must. It may be to merge the coverage of unit tests and osgi tests together. It could also be extended to generate coverage of tests across repos as well. For example, we have a repo

[Dev] [UUF] Feature request - Print a custom message in console on startup.

$subject app.yaml welcomeMessage: "{{config.appName}} started at {{appUrl}} -- With regards, *Manu*ranga Perera. phone : 071 7 70 20 50 mail : m...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Error while validating the signature in SAML Grant Type

Hi All, This is an update to provide more context to the problem. Currently in IoT Server we have device type apis for each tenants that are exposed through api manager. In order to access it we create an AM Application and then we subscribe to the tenants apis. This works fine when we use the

Re: [Dev] Merging multiple Jacoco coverages together

Thanks Niranjan. We can re-use the same! :-) @Dharshana, per component coverage report is already there. The aggregated report is in addition to that. The aggregated report will depict the overall coverage of the repo to understand how much of this repo's code are covered. Both these are

Re: [Dev] Merging multiple Jacoco coverages together

Hi KasunG / Dharshana, On Mon, Jan 16, 2017 at 9:34 PM, KasunG Gajasinghe wrote: > Hi Dharshana, > > To get a proper understanding of the actual coverage, merging of all the > jacoco coverages is a must. It may be to merge the coverage of unit tests > and osgi tests together.

Re: [Dev] Merging multiple Jacoco coverages together

Hi All, Considering a component the component should depict a coverage in a single coverage report. As our current tests in Kernal it seems we have coverage per repo. But for componats we have to consider coverage in component separately. There for we have to consider coverage per component

Re: [Dev] [UUF] Feature request - Print a custom message in console on startup.

Hi Manu, We have implemented something similar in [1] where we print the URI's of the available apps which I believe address your requirement as well. The need for such a log would be to notify that the app has been deployed successfully and to get the app url. On the other hand, the app

Re: [Dev] Print UUF Application URLs in server startup logs

Hi All, This feature is implemented and available in the latest snapshot (1.0.0-SNAPSHOT) of 'carbon-uuf'. Thanks. On Fri, Jan 13, 2017 at 10:28 AM, KasunG Gajasinghe wrote: > > On Fri, Jan 13, 2017 at 10:14 AM, Kishanthan Thangarajah < > kishant...@wso2.com> wrote: > >>

Re: [Dev] STS Client sample Doesn't work for Non-repudiation

Hi Hasintha, Thanks for providing the solution. It worked fine after changing the *path.policy.sts* property to *sts-policy-signonly.xml *in the client.properties file. In the default sample it was sts-policy-ut.xml. Even though it worked for UsernameToken scenario, it needs to be changed for