Hi Devs,
This is to discuss subject.
*Requirement:*
Once an API is exported, its possible to be directly imported in to another
APIM deployment in a separate environment. For an admin user, it should be
possible to export all APIs in one deployment to another one.
The following information
Hi all,
We are calling off the RC1 vote due to above identified issues. We will
do a RC2 soon.
Thanks!
Malintha
On Mon, Jan 9, 2017 at 12:57 PM, Ayoma Wijethunga wrote:
> [-] Broken - do not release (Due to a security related issue identified)
>
> Thank you,
> Ayoma.
>
> On
+1
On Fri, Jan 6, 2017 at 3:23 PM, SajithAR Ariyarathna
wrote:
> Hi All,
>
> We are hoping to do $subject.
>
> *UUF Component:*
>
> Currently a UUF component has two configuration files, 'component.yaml'
> and 'config.yaml'. 'component.yaml' contains APIs entries and bindings
Hi all,
Thanks for testing WSO2 Identity Server 5.3.0-RC3. This vote passed with 22
+1s and 0 -1s.
We will proceed with WSO2 Identity Server 5.3.0 release.
--
*Pulasthi Mahawithana*
Senior Software Engineer
WSO2 Inc., http://wso2.com/
Mobile: +94-71-5179022
Blog: http://blog.pulasthi.org
Hi,
Tested the following,
- Custom OAuth 2.0 grant-type
- Integrated Windows Authentication (IWA) with Kerberos
[+] Stable - go ahead and release
On Mon, Jan 9, 2017 at 2:55 PM, Pulasthi Mahawithana
wrote:
> Hi All,
>
> Tested the following,
>
>- Engaging
Hi Manu,
1. We haven't finalize the widget related config yet... but look like there
is only few details available and those are not sensitive.
- Widget ID
- Title
- Description
- Thumbnail URL
- Permission (this might be a permission string or role, this discussion is
still going on)
(But in
Hi Nipuna,
1. Can you give a sample of a widget related detail?
2. What is the difference between a widget and a UUF fragment
--
With regards,
*Manu*ranga Perera.
phone : 071 7 70 20 50
mail : m...@wso2.com
___
Architecture mailing list
For dashboard, I think storing widget data in a separate location would be
better.
On Mon, Jan 9, 2017 at 3:23 PM, Chandana Napagoda wrote:
> Hi Sajith,
>
> What is our recommendation on data which can be stored in the
> component.yaml file? As an example, widget related
Hi,
Tested the following IS features.
1. PDF Support in IS analytics
2. Email notifications on Security Alerts in IS analytics
[+] Stable - go ahead and release
On Mon, Jan 9, 2017 at 1:14 PM, Rasika Perera wrote:
> Tested out component version 5.7.0 with IoT pack.
>
Hi All,
Tested the following,
- Engaging access policies in authentication flow
- Template XACML policies for authentication flow and rule based
provisioning
- XACML funtionalities and policy editor
- SCIM user list with attributes and other SCIM operations
- Prompt for missing
Tested following features in RC3
- Install API Manager 6.0.37 features with IS RC3 pack
- Tested API Creation, Application Creation, Key generation and API
Invocation in both super tenant and tenant mode
- Tested SSO of API Store and Publisher in both super tenant and tenant
mode
Hi Chandana,
It is better to keep a separate file as those are widget level
configuration. But problem of keeping a separate file is that we cannot
read the data from that file unless we make it public. We haven't decide
what type of configs will be available for widget but if there are
sensitive
Hi,
Tested following,
- Account recovery with notification
- Account recovery with security questions
- Recaptcha
- Self signup
[+] Stable - go ahead and release
Thanks,
Thanuja
On Mon, Jan 9, 2017 at 11:05 AM, Rushmin Fernando wrote:
> Tested following
Tested out component version 5.7.0 with IoT pack.
[+] Stable - go ahead and release
On Mon, Jan 9, 2017 at 1:00 PM, Ashen Weerathunga wrote:
> Hi,
>
> Tested the following IS Analytics features with IS Runtime,
>
>- Login attempts analytics
>- Login session analytics
Tested following features in RC3.
- XACML Rest profile
- Rule base provisioning
- Authorization Rules for SSO
- Dynamic Client Registration
[+] Stable : Go ahead and release
Thanks,
On Mon, Jan 9, 2017 at 1:00 PM, Ashen Weerathunga wrote:
> Hi,
>
> Tested the
On Mon, Jan 9, 2017 at 1:34 PM, SajithAR Ariyarathna
wrote:
> Currently, we are in the process of refactoring the carbon-security source
>> and hope to release a 1.0.0-m3 soon. With this release, CAAS User
>> implementation will only provide authorization functionalities. In
+1
On Fri, Jan 6, 2017 at 3:23 PM, SajithAR Ariyarathna
wrote:
> Hi All,
>
> We are hoping to do $subject.
>
> *UUF Component:*
>
> Currently a UUF component has two configuration files, 'component.yaml'
> and 'config.yaml'. 'component.yaml' contains APIs entries and bindings
>
> Currently, we are in the process of refactoring the carbon-security source
> and hope to release a 1.0.0-m3 soon. With this release, CAAS User
> implementation will only provide authorization functionalities. In order to
> consume identity store related functionalities, you need to use the
18 matches
Mail list logo