[Dev] [IAM] Loading Function Libraries to Authentication Scripts

[Anuradha Karunarathna]

Hi All,


I’m working on a project to use function libraries in adaptive
authentication scripts and a component to manage function
libraries(add/list/delete/edit/export/import) [1]. I have implemented a
carbon component to manage function libraries with add/list/delete and edit
features[2].

Then, I researched possible ways to include the implemented function
libraries to adaptive authentication scripts and make the functions in the
library could be used in the authentication scripts.  Nashorn – (the new
default JavaScript engine for the JVM as of Java 8.)[3] has the capability
to load and evaluate additional script files quite easily with ‘load()’
function. It loads and evaluates script from a file or a URL or a script
object.

load(file path of the function library);

or

load(URL to the function library);

or

load({script:”function library script”, name:”library name”});

needs to be added on top of the authentication script.

However, directly using load function in authentication script is not a
user-friendly option. If so, the user needs to know either file path to the
needed function library, or URL or the content and the name of the function
library. Therefore,  I added a new function under core functions in
adaptive authentication JS API reference[4] as “loadLocalLibrary(‘’)” . Inside that function, retrieving the relevant function
library from database and load() function evaluation is done. Then, the
user has to add “loadLocalLibrary(‘’);” on top of
the authentication script or before an usage of a function in the function
library. Hence, the user needs to know only the function library name.

Moreover, over the three options available to load and evaluate the script,
script object method is selected.


Reasons to reject the other two methods:

File path: need to write a file with the content of the loaded function
library from DB. So, file writings inside the IS cause for security issues.

URL: Need an addition REST service and having a network call is an overhead.


engine.eval(“load({name:“library name”, script:“function library
script”})”) is used inside the loadLocalLibrary(String name) core function
to evaluate the function library script.


This diagram illustrates the above described process.


If you have any other possible solutions or suggestions regarding the above
scenario, feel free to discuss.

References

[1] [IAM]Function Library for adaptive authentication

[2]https://github.com/AnuradhaSK/Function-Library-Manager

[3]https://docs.oracle.com/javase/9/nashorn/JSNUG.pdf

[4]
https://docs.wso2.com/display/IS570/Adaptive+Authentication+JS+API+Reference#AdaptiveAuthenticationJSAPIReference-Corefunctions


*Anuradha Karunarathna*
Intern-Software Engineering | WSO2,inc.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Upgrading C4 OSGi to support Java 10

[Ruwan Abeykoon]

Hi All,

Created
https://github.com/wso2/carbon-kernel/tree/4.4.x_java10

I do not have permission to following repos. I added respective owners on
this tread.

maven-tools
carbon-metrics
carbon-apimgt
product-apim

Cheers,
Ruwan

On Thu, Oct 11, 2018 at 10:42 AM Tharindu Wijewardane 
wrote:

> Hi Ruwan,
>
> Will you be able to create following new branches. Once created I will
> send PRs to those new branches.
>
> WSO2 repo
>
> Base branch
>
> New branch
>
> maven-tools
>
> master
>
> master_java10
>
> carbon-kernel
>
> 4.4.x
>
> 4.4.x_java10
>
> carbon-metrics
>
> 1.x.x
>
> 1.x.x_java10
>
> carbon-apimgt
>
> 6.x
>
> 6.x_java10
>
> product-apim
>
> 2.x
>
> 2.x_java10
>
> Thanks
>
> On Mon, Oct 8, 2018 at 10:39 AM Tharindu Wijewardane 
> wrote:
>
>> Hi all,
>>
>> Carbon kernel can be now started on java 10 without any exceptions. The
>> management console is accessible through a web browser. Also all the tests
>> in maven build are passing (java 8).
>>
>> Moving onto the APIM,
>> As I mentioned in a previous email, I temporally commented out following
>> 3 feature groups in order to build the APIM.
>>
>> org.wso2.carbon.apimgt.keymanager.feature.group
>> org.wso2.carbon.apimgt.feature.group
>> org.wso2.carbon.apimgt.store.feature.group
>>
>> Those feature groups require upgrading OSGi in IS related libraries and
>> there are several of them.
>>
>> Moving forward without those for now, when the APIM product is started
>> there are some exceptions and errors. (Now that the logs are working those
>> errors are visible.)
>>
>>
>> *[2018-10-07 21:17:53,314] FATAL - ServiceBusInitializer Failed to
>> initialize ESB due to a fatal error*
>> *java.lang.NoClassDefFoundError: sun/misc/Service*
>> * at
>> org.apache.synapse.config.xml.ConfigurationFactoryAndSerializerFinder.registerExtensions(ConfigurationFactoryAndSerializerFinder.java:117)*
>> * at
>> org.apache.synapse.config.xml.ConfigurationFactoryAndSerializerFinder.loadConfigurationFatoriesAndSerializers(ConfigurationFactoryAndSerializerFinder.java:105)*
>> * at
>> org.apache.synapse.config.xml.ConfigurationFactoryAndSerializerFinder.getInstance(ConfigurationFactoryAndSerializerFinder.java:70)*
>> *...*
>> *Caused by: java.lang.ClassNotFoundException: sun.misc.Service cannot be
>> found by synapse-core_2.1.7.wso2v78*
>> * at
>> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:448)*
>>
>> *[2018-10-07 21:17:53,881] ERROR - ApplicationRegistry
>> java.lang.ExceptionInInitializerError*
>> *[2018-10-07 21:17:53,882] ERROR - Main Exception during startup.
>> Triggering shutdown *
>> *org.wso2.andes.kernel.AndesException: Unable to initialise application
>> registry*
>> * at org.wso2.andes.server.Broker.startupImpl(Broker.java:307)*
>> * at org.wso2.andes.server.Broker.startup(Broker.java:110)*
>> *...*
>> *Caused by: java.lang.IllegalStateException: Metric Service is not
>> available!*
>> * at
>> org.wso2.carbon.metrics.manager.ServiceReferenceHolder.getMetricService(ServiceReferenceHolder.java:40)*
>>
>> Those seems to be related to Synapse and Andes.
>>
>> Thanks
>>
>> On Wed, Oct 3, 2018 at 6:29 PM Selvaratnam Uthaiyashankar <
>> shan...@wso2.com> wrote:
>>
>>> Great!. Thanks for the update.
>>>
>>> On Wed, Oct 3, 2018 at 11:22 AM Tharindu Wijewardane 
>>> wrote:
>>>
 Hi all,

 With the help of eclipse community I got to know that they have removed
 org.eclipse.osgi.service.resolver.PlatformAdmin service from the osgi
 framework in Luna version and adding the
 bundle: org.eclipse.osgi.compatibility.state to Carbon runtime feature
 fixed the missing service issue. Now All the bundles which are in active
 state with java 8 are in Active state with java 10 too.

 Also the issue with CarbonConsoleAppender (NoClassDefFoundError: Could
 not initialize class CarbonContextDataHolder) could be fixed by adding
 deprecated javax classes back to the classpath. It fixed some other similar
 issues which ware due to the missing javax.activation and javax.xml 
 classes.
 Now the logs are printed on the osgi terminal using the
 CarbonConsoleAppender itself.

 Now the only remaining issue with Carbon kernel (as it seems) is a set
 of tomcat exceptions. I am currently working on it.

 Thanks

 On Thu, Sep 27, 2018 at 3:01 PM Tharindu Wijewardane <
 tharin...@wso2.com> wrote:

> Hi all,
>
> The logs were not getting printed because following exception is
> thrown through CarbonConsoleAppender.
>
> "NoClassDefFoundError: Could not initialize class
> CarbonContextDataHolder"
>
> CarbonContextDataHolder has a set of javax.naming* imports and since
> java 10 has deprecated using them I added jndi jar which contains those
> classes in to a folder inside the pack and modifies the wso2server.sh to
> add those to the classpath. Also I added the jars in endorsed dir to the
> classpath since extension 

Re: [Dev] Upgrading C4 OSGi to support Java 10

[Tharindu Wijewardane]

Hi Ruwan,

Will you be able to create following new branches. Once created I will send
PRs to those new branches.

WSO2 repo

Base branch

New branch

maven-tools

master

master_java10

carbon-kernel

4.4.x

4.4.x_java10

carbon-metrics

1.x.x

1.x.x_java10

carbon-apimgt

6.x

6.x_java10

product-apim

2.x

2.x_java10

Thanks

On Mon, Oct 8, 2018 at 10:39 AM Tharindu Wijewardane 
wrote:

> Hi all,
>
> Carbon kernel can be now started on java 10 without any exceptions. The
> management console is accessible through a web browser. Also all the tests
> in maven build are passing (java 8).
>
> Moving onto the APIM,
> As I mentioned in a previous email, I temporally commented out following 3
> feature groups in order to build the APIM.
>
> org.wso2.carbon.apimgt.keymanager.feature.group
> org.wso2.carbon.apimgt.feature.group
> org.wso2.carbon.apimgt.store.feature.group
>
> Those feature groups require upgrading OSGi in IS related libraries and
> there are several of them.
>
> Moving forward without those for now, when the APIM product is started
> there are some exceptions and errors. (Now that the logs are working those
> errors are visible.)
>
>
> *[2018-10-07 21:17:53,314] FATAL - ServiceBusInitializer Failed to
> initialize ESB due to a fatal error*
> *java.lang.NoClassDefFoundError: sun/misc/Service*
> * at
> org.apache.synapse.config.xml.ConfigurationFactoryAndSerializerFinder.registerExtensions(ConfigurationFactoryAndSerializerFinder.java:117)*
> * at
> org.apache.synapse.config.xml.ConfigurationFactoryAndSerializerFinder.loadConfigurationFatoriesAndSerializers(ConfigurationFactoryAndSerializerFinder.java:105)*
> * at
> org.apache.synapse.config.xml.ConfigurationFactoryAndSerializerFinder.getInstance(ConfigurationFactoryAndSerializerFinder.java:70)*
> *...*
> *Caused by: java.lang.ClassNotFoundException: sun.misc.Service cannot be
> found by synapse-core_2.1.7.wso2v78*
> * at
> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:448)*
>
> *[2018-10-07 21:17:53,881] ERROR - ApplicationRegistry
> java.lang.ExceptionInInitializerError*
> *[2018-10-07 21:17:53,882] ERROR - Main Exception during startup.
> Triggering shutdown *
> *org.wso2.andes.kernel.AndesException: Unable to initialise application
> registry*
> * at org.wso2.andes.server.Broker.startupImpl(Broker.java:307)*
> * at org.wso2.andes.server.Broker.startup(Broker.java:110)*
> *...*
> *Caused by: java.lang.IllegalStateException: Metric Service is not
> available!*
> * at
> org.wso2.carbon.metrics.manager.ServiceReferenceHolder.getMetricService(ServiceReferenceHolder.java:40)*
>
> Those seems to be related to Synapse and Andes.
>
> Thanks
>
> On Wed, Oct 3, 2018 at 6:29 PM Selvaratnam Uthaiyashankar <
> shan...@wso2.com> wrote:
>
>> Great!. Thanks for the update.
>>
>> On Wed, Oct 3, 2018 at 11:22 AM Tharindu Wijewardane 
>> wrote:
>>
>>> Hi all,
>>>
>>> With the help of eclipse community I got to know that they have removed
>>> org.eclipse.osgi.service.resolver.PlatformAdmin service from the osgi
>>> framework in Luna version and adding the
>>> bundle: org.eclipse.osgi.compatibility.state to Carbon runtime feature
>>> fixed the missing service issue. Now All the bundles which are in active
>>> state with java 8 are in Active state with java 10 too.
>>>
>>> Also the issue with CarbonConsoleAppender (NoClassDefFoundError: Could
>>> not initialize class CarbonContextDataHolder) could be fixed by adding
>>> deprecated javax classes back to the classpath. It fixed some other similar
>>> issues which ware due to the missing javax.activation and javax.xml classes.
>>> Now the logs are printed on the osgi terminal using the
>>> CarbonConsoleAppender itself.
>>>
>>> Now the only remaining issue with Carbon kernel (as it seems) is a set
>>> of tomcat exceptions. I am currently working on it.
>>>
>>> Thanks
>>>
>>> On Thu, Sep 27, 2018 at 3:01 PM Tharindu Wijewardane 
>>> wrote:
>>>
 Hi all,

 The logs were not getting printed because following exception is thrown
 through CarbonConsoleAppender.

 "NoClassDefFoundError: Could not initialize class
 CarbonContextDataHolder"

 CarbonContextDataHolder has a set of javax.naming* imports and since
 java 10 has deprecated using them I added jndi jar which contains those
 classes in to a folder inside the pack and modifies the wso2server.sh to
 add those to the classpath. Also I added the jars in endorsed dir to the
 classpath since extension class loader is not present in jdk 10 and classes
 in endorsed dir location is not automatically loaded.
 Still I could not solve the above issue and decided to use the default
 log4j ConsoleAppender instead of CarbonConsoleAppender for now.

 When I compare the carbon kernel bundles in Active state in java 8 and
 java 10 environments I noticed following bundles are not activated in java
 10 env.

 org.wso2.carbon.base
 org.wso2.carbon.core
 

[Dev] Dynamic Max Records on DSS

[Júnior]

Hello,

I have a DSS Service that calls a stored procedure and this procedure can
return a huge result set 10k+ records. I saw in the documentation we can
set Max Rows property in the query to control how many records it will
return.

Is it possible to define this property in runtime, I mean by passing
parameter to the service that would be used in the configuration? Or this
is possible only by redeploying the service?

Thanks,
-- 
Francisco Ribeiro
*SCEA|SCJP|SCWCD|IBM Certified SOA Associate*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Retry an Endpoint

[Júnior]

Hi Kamidu,

but this retry, it will be done in the same request, or it is just a number
of times the endpoint will be used before being set as suspended? At least
this is what I understood from the documentation.

Thanks,

Em qua, 10 de out de 2018 às 10:11, Kamidu Sachith Punchihewa <
sachi...@wso2.com> escreveu:

> Hi Junior,
> You have the ability to configure the retry option and count when creating
> the endpoint. Please refer the below sample configuration,
>
> http://ws.apache.org/ns/synapse; name="sample">
>>http://localhost:8080/sample/echo;>
>>   
>>  1.0
>>   
>>   
>>  5
>>  600
>>   
>>   
>>  1
>>  fault
>>   
>>
>> 
>
>
> The above configuration is enabling the endpoint to be retried 5 times
> with a timeout.
>
> You can create a replay of the messages to the endpoint with more control
> by following the store forward integration pattern. Please refer to the
> documentation [1] for more information.
>
> [1]
> https://docs.wso2.com/display/ESB480/Store+and+Forward+Using+JMS+Message+Stores
>
> Thanks and Best Regards,
>
> On Mon, Oct 8, 2018 at 2:14 AM Júnior  wrote:
>
>> Hi,
>>
>> I would like to know if there is a way of retrying an endpoint
>> automatically in WSO2 ESB.
>>
>> As I could see one way of doing that is using the failover mediator with
>> some leaf endpoints.
>>
>> I would like to a scenario like this:
>>
>> Try the endpoint and in case of a timeout, try it another two times and
>> after a third try it would lead to a fault sequence. Using the failover
>> mediator, it will work only if we enable the suspension of the endpoint.
>> I would like to have it without adding suspension settings. As I could
>> see, without the suspension settings, the failover endpoint will try the
>> request forever until the endpoints respond correctly.
>>
>> Is there any way to achieve this scenario?
>>
>> My first idea, in case there is no OOTB solution, would be:
>>
>> 1. create a sequence that would have the call/send mediator. This
>> sequence, would have a onError sequence, so in case of a timeout, we would
>> have a condition for a retry;
>> 2. In case of timeout, the onError would be called, and we would have a
>> counter, in case the counter is less than 3, we would call the previous
>> sequence, else, it would fault.
>>
>> Would this be a correct approach for this scenario?
>>
>> Thanks,
>> --
>> Francisco Ribeiro
>> *SCEA|SCJP|SCWCD|IBM Certified SOA Associate*
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>
>
> --
>
> *Kamidu Sachith Punchihewa *| Senior Software Engineer | *WSO2 Inc*.
> (m) +94770566749 / +254778872783 | (e) sachi...@wso2.com | (ln) kamidu
> 
>
> 
>


-- 
Francisco Ribeiro
*SCEA|SCJP|SCWCD|IBM Certified SOA Associate*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [IS 560] Adaptive authentication - How to handle retry scenarios

[Hasitha De Silva]

Hi,

I'm having some trouble trying to simulate the login failure scenarios with
conditional auth scripts. What is the ideal way to enforce the script to
retry login attempts ?

Right now my script is as below;

function onLoginRequest(context) {
executeStep(1, {
onSuccess: function(context) {
if (!checkIP(context)) {
if (!checkIPInSubnet(context)) {
if (step2CheckEmail(context)) {
executeStep(2, {
onFail: function(context) {
executeStep(2);
}
});
}
}
}
},
onFail: function(context) {
executeStep(1);
}
});
}

The expected flow is that the user is taken to the email otp page after
basic login, and then, if he/she enters the wrong OTP code, the user should
be allowed to retry another OTP code. However, what actually happens is
that the user is taken to a default IS error page with following error
trace :

[2018-10-10 15:26:01,298] ERROR
{org.wso2.carbon.identity.application.authentication.framework.handler.step.impl.DefaultStepHandler}
-  Code mismatch
org.wso2.carbon.identity.application.authentication.framework.exception.AuthenticationFailedException:
Code mismatch
at
org.wso2.carbon.identity.authenticator.emailotp.EmailOTPAuthenticator.processAuthenticationResponse(EmailOTPAuthenticator.java:242)
at
org.wso2.carbon.identity.application.authentication.framework.AbstractApplicationAuthenticator.process(AbstractApplicationAuthenticator.java:77)
at
org.wso2.carbon.identity.authenticator.emailotp.EmailOTPAuthenticator.process(EmailOTPAuthenticator.java:125)
at
org.wso2.carbon.identity.application.authentication.framework.handler.step.impl.DefaultStepHandler.doAuthentication(DefaultStepHandler.java:490)

[2018-10-10 15:26:01,362] ERROR
{org.wso2.carbon.identity.application.authentication.framework.handler.request.impl.DefaultRequestCoordinator}
-  Exception in Authentication Framework
java.lang.NullPointerException
at
org.wso2.carbon.extension.identity.helper.FederatedAuthenticatorUtil.setUsernameFromFirstStep(FederatedAuthenticatorUtil.java:399)
at
org.wso2.carbon.identity.authenticator.emailotp.EmailOTPAuthenticator.initiateAuthenticationRequest(EmailOTPAuthenticator.java:160)
at
org.wso2.carbon.identity.application.authentication.framework.AbstractApplicationAuthenticator.process(AbstractApplicationAuthenticator.java:71)
at
org.wso2.carbon.identity.authenticator.emailotp.EmailOTPAuthenticator.process(EmailOTPAuthenticator.java:125)


Appreciate any help :)


Best Regards,
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [3.0.0] - JWT Token Generation in API Manager

[Pubudu Gunatilaka]

Hi Tharindu,

On Tue, Oct 9, 2018 at 5:37 PM Tharindu Dharmarathna 
wrote:

> Hi All,
>>
>> *Problem*
>>
>> In order to generate token as JWT for specific applications, we need to
>> switch the Token Generation implementation according to some application
>> level property.
>>
>> *Solutions*
>>
>> 1. Change DCRM rest API to register Application as JWT token issuer.
>>
>
+1 for this option. I feel this is the most suitable option.

Thank you!
-- 
*Pubudu Gunatilaka*
Committer and PMC Member - Apache Stratos
Senior Software Engineer
WSO2, Inc.: http://wso2.com
mobile : +94774078049 <%2B94772207163>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Retry an Endpoint

[Kamidu Sachith Punchihewa]

Hi Junior,
You have the ability to configure the retry option and count when creating
the endpoint. Please refer the below sample configuration,

http://ws.apache.org/ns/synapse; name="sample">
>http://localhost:8080/sample/echo;>
>   
>  1.0
>   
>   
>  5
>  600
>   
>   
>  1
>  fault
>   
>
> 


The above configuration is enabling the endpoint to be retried 5 times with
a timeout.

You can create a replay of the messages to the endpoint with more control
by following the store forward integration pattern. Please refer to the
documentation [1] for more information.

[1]
https://docs.wso2.com/display/ESB480/Store+and+Forward+Using+JMS+Message+Stores

Thanks and Best Regards,

On Mon, Oct 8, 2018 at 2:14 AM Júnior  wrote:

> Hi,
>
> I would like to know if there is a way of retrying an endpoint
> automatically in WSO2 ESB.
>
> As I could see one way of doing that is using the failover mediator with
> some leaf endpoints.
>
> I would like to a scenario like this:
>
> Try the endpoint and in case of a timeout, try it another two times and
> after a third try it would lead to a fault sequence. Using the failover
> mediator, it will work only if we enable the suspension of the endpoint.
> I would like to have it without adding suspension settings. As I could
> see, without the suspension settings, the failover endpoint will try the
> request forever until the endpoints respond correctly.
>
> Is there any way to achieve this scenario?
>
> My first idea, in case there is no OOTB solution, would be:
>
> 1. create a sequence that would have the call/send mediator. This
> sequence, would have a onError sequence, so in case of a timeout, we would
> have a condition for a retry;
> 2. In case of timeout, the onError would be called, and we would have a
> counter, in case the counter is less than 3, we would call the previous
> sequence, else, it would fault.
>
> Would this be a correct approach for this scenario?
>
> Thanks,
> --
> Francisco Ribeiro
> *SCEA|SCJP|SCWCD|IBM Certified SOA Associate*
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>


-- 

*Kamidu Sachith Punchihewa *| Senior Software Engineer | *WSO2 Inc*.
(m) +94770566749 / +254778872783 | (e) sachi...@wso2.com | (ln) kamidu



___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 API Manager 2.6.0 Released!

[Chamila Adhikarinayake]

+ announce

On Wed, Oct 10, 2018 at 2:12 PM, Fazlan Nazeem  wrote:

> WSO2 API Manager 2.6.0 Released!
> The WSO2 API Manager team is pleased to announce the release of version
> 2.6.0 of WSO2 API Manager.
>
> WSO2 API Manager is a platform for creating, managing, consuming and
> monitoring APIs. It employs proven SOA best practices to solve a wide range
> of API management challenges such as API provisioning, API governance, API
> security and API monitoring. It combines some of the most powerful and
> mature components of the WSO2's state-of-the-art Carbon platform to deliver
> a smooth and end-to-end API management experience while catering to both
> API publisher and API consumer requirements.
>
> WSO2 API Manager is comprised of several modules.
>
>
>- API Provider: Define new APIs and manage them
>- API Store: Browse published APIs and subscribe to them
>- API Gateway: The underlying API runtime based on WSO2 ESB
>- API Key Manager: Performs Key Generation and Key Validation
>functionalities
>- API Traffic Manager: Performs Rate Limiting of API Requests
>
> For more information on WSO2 API Manager please visit
> https://wso2.com/api-management/install/. Also, take a look at the online
> product documentation .How to Run
>
>1. Extract the downloaded zip
>2. Go to the bin directory in the extracted folder
>3. Run the wso2server.sh or wso2server.bat as appropriate
>4. Launch a web browser and navigate to https://localhost:9443/
>publisher to access the API publisher web app
>5. Navigate to https://localhost:9443/store to access the API store
>6. Navigate to https://localhost:9443/admin to access Admin Portal
>7. Use "admin", "admin" as the username and password to log in as an
>admin
>
> New Features in this Release
>
> Visit About this release
>  to find out the
> features introduced in this release.
>
> *Bug Fixes and Improvements in 2.6.0*
>
>- GitHub (product-apim
>
>)
>- GitHub (carbon-apimgt
>
> 
>)
>
> *Known Issues*
>
> All the open issues pertaining to WSO2 API Manager are reported at the
> following location:
>
> GitHub (product-apim ),
> (analytics-apim
> )
>
>
> *How You Can Contribute*
>
> *Mailing Lists*
> Join our mailing list and correspond with the developers directly.
>
>
>- Developer List: dev@wso2.org | Subscribe | Mail Archive
>
>- User List: u...@wso2.org | Subscribe | Mail Archive
>
>
> *Reporting Issues*
>
> We encourage you to report issues, documentation faults, and feature
> requests regarding WSO2 API Manager through the public API Manager Git
> Repo. 
> -- The WSO2 API Manager Team --
>
> --
> Thanks & Regards,
>
> *Fazlan Nazeem*
> Senior Software Engineer
> WSO2 Inc
> Mobile : +94772338839
> fazl...@wso2.com
>



-- 
Regards,
Chamila Adhikarinayake
Associate Technical Lead
WSO2, Inc.
Mobile - +94712346437
Email  - chami...@wso2.com
Blog  -  http://helpfromadhi.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 API Manager 2.6.0 Released!

[Fazlan Nazeem]

WSO2 API Manager 2.6.0 Released!
The WSO2 API Manager team is pleased to announce the release of version
2.6.0 of WSO2 API Manager.

WSO2 API Manager is a platform for creating, managing, consuming and
monitoring APIs. It employs proven SOA best practices to solve a wide range
of API management challenges such as API provisioning, API governance, API
security and API monitoring. It combines some of the most powerful and
mature components of the WSO2's state-of-the-art Carbon platform to deliver
a smooth and end-to-end API management experience while catering to both
API publisher and API consumer requirements.

WSO2 API Manager is comprised of several modules.


   - API Provider: Define new APIs and manage them
   - API Store: Browse published APIs and subscribe to them
   - API Gateway: The underlying API runtime based on WSO2 ESB
   - API Key Manager: Performs Key Generation and Key Validation
   functionalities
   - API Traffic Manager: Performs Rate Limiting of API Requests

For more information on WSO2 API Manager please visit
https://wso2.com/api-management/install/. Also, take a look at the online
product documentation .How to Run

   1. Extract the downloaded zip
   2. Go to the bin directory in the extracted folder
   3. Run the wso2server.sh or wso2server.bat as appropriate
   4. Launch a web browser and navigate to https://localhost:9443/publisher
   to access the API publisher web app
   5. Navigate to https://localhost:9443/store to access the API store
   6. Navigate to https://localhost:9443/admin to access Admin Portal
   7. Use "admin", "admin" as the username and password to log in as an
   admin

New Features in this Release

Visit About this release
 to find out the
features introduced in this release.

*Bug Fixes and Improvements in 2.6.0*

   - GitHub (product-apim
   
   )
   - GitHub (carbon-apimgt
   

   )

*Known Issues*

All the open issues pertaining to WSO2 API Manager are reported at the
following location:

GitHub (product-apim ), (
analytics-apim )


*How You Can Contribute*

*Mailing Lists*
Join our mailing list and correspond with the developers directly.


   - Developer List: dev@wso2.org | Subscribe | Mail Archive
   
   - User List: u...@wso2.org | Subscribe | Mail Archive
   

*Reporting Issues*

We encourage you to report issues, documentation faults, and feature
requests regarding WSO2 API Manager through the public API Manager Git Repo.

-- The WSO2 API Manager Team --

-- 
Thanks & Regards,

*Fazlan Nazeem*
Senior Software Engineer
WSO2 Inc
Mobile : +94772338839
fazl...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 Identity Server 5.7.0 Released!

[Nuwandi Wickramasinghe]

The WSO2 Identity Server team is pleased to announce the release of WSO2
Identity Server version 5.7.0.

The WSO2 Identity Server is a uniquely extensible, open source IAM product
optimized for identity federation and SSO with comprehensive support for
adaptive and strong authentication. It supports a wide array of
authentication protocols such as SAML 2.0 Web SSO, OAuth 2.0/1.0a, OpenID
Connect, and WS-Federation Passive. It supports role based authorization
and fine grained authorization with XACML 2.0/3.0 while inbound/outbound
provisioning is supported through SCIM and SPML.

WSO2 Identity Server is developed on top of the revolutionary WSO2 Carbon
platform, an OSGi based framework that provides seamless modularity to your
SOA solution via componentization.

All the major features have been developed as pluggable Carbon components.

You can download this distribution from
https://wso2.com/identity-and-access-management/install

Online documentation is available at
http://docs.wso2.org/wiki/display/IS570/WSO2+Identity+Server+Documentation
.
How to Run

   1.

   Extract the downloaded zip file.
   2.

   Go to the bin directory in the extracted folder.
   3.

   Run the wso2server.sh or wso2server.bat file as appropriate.
   4.

   Optionally, if you need to start the OSGi console with the server, use
   the -DosgiConsole property when starting the server.

New Features in this Release

WSO2 Identity Server version 5.7.0 is part of WSO2’s 2018 Fall Release
which includes new features and updates across all products, solutions, and
services.

The following includes major features and improvements provided in WSO2 IS
5.7.0:


   -

   Adaptive Authentication - Adaptive authentication is a secure and
   flexible form of authentication where you need to validate multiple factors
   to determine the authenticity of a login attempt, before you grant access
   to a resource. Following evaluation criteria should be met to perform
   adaptive authentication,
   -

  User attributes
  -

  User behavior
  -

  Level of assurance with regard to the access request
  -

  Risk analysis statistics
  -

  Machine learning algorithms
  -

   User Managed Access(UMA) 2.0 - UMA is an protocol written using OAuth2
   protocol, to provide the resource owner to control the authorization of
   data sharing and other protected-resource access made between online
   services on the owner’s behalf, or with the owner’s authorization by an
   autonomous requesting party. WSO2 Identity Server currently supports basic
   level UMA features which users can control through provided APIs.
   -

   Integration with Office 365 - With this feature, WSO2 Identity Server
   acts as the Identity Provider and handles user synchronization with
   Microsoft cloud. Role based on-demand user synchronization and the group
   based license management are the two special features of WSO2 IS
solution. It
   also provides heterogeneous user store support, multi-factor authentication
   and SSO/SLO with other enterprise and community application.


This release includes functional improvements and fixes to the product. The
complete list of improvements and bug fixes available with the release can
be found at the following locations:


   -

   5.7.0-RC2 Fixes
   
   -

   5.7.0-RC1 Fixes
   
   -

   5.7.0-Beta2 Fixes
   
   -

   5.7.0-Beta Fixes
   
   -

   5.7.0-Alpha3 Fixes
   
   -

   5.7.0-Alpha2 Fixes
   
   -

   5.7.0-Alpha Fixes
   
   -

   5.7.0-M5 Fixes 
   -

   5.7.0-M4 Fixes 
   -

   5.7.0-M3 Fixes 
   -

   5.7.0-M2 Fixes 
   -

   5.7.0-M1 Fixes 

Known Issues

All the open issues pertaining to WSO2 Identity Server are reported at the
following locations:

IS Runtime 

IS Analytics 
How You Can ContributeMailing Lists

Join our mailing list and correspond with the developers directly. We also
encourage you to take part in discussions related to the product in the
architecture mailing list. If you have any questions regarding the product
you can use our StackOverflow forum to raise them as well.


   -

   Developer list: dev@wso2.org | Subscribe | 

Re: [Dev] [Announce] [Architecture] WSO2 Product Installation Resources Released!!!

[Chiranga Alwis]

Hi Youcef,

Currently, we have created Kubernetes resources for only patterns 1 and 2
of WSO2 API Manager 2.6.0. Kubernetes resources for WSO2 API Manager
patterns 3 and 4 are only available for version 2.1.0 [1] at the moment.

Kubernetes resources for patterns 3 and 4 for the latest versions of WSO2
API Manager are expected to be part of the next immediate release.

[1]: https://github.com/wso2/kubernetes-apim/tree/2.1.x


On Wed, Oct 10, 2018 at 10:25 AM Nuwan Dias  wrote:

>
>
> On Wed, Oct 10, 2018 at 10:22 AM Vimukthi Perera 
> wrote:
>
>> Hi Nuwan,
>>
>> On Wed, Oct 10, 2018 at 7:36 AM Nuwan Dias  wrote:
>>
>>> Hi Vimukthi,
>>>
>>> Why is it that the API Manager artifacts have a 4 digit versioning and
>>> the others have the standard 3 digit versioning?
>>>
>>> All the producs have the 4 digit versioning. Please see the link. It was
>> my mistake that I have added the release tag to the Name in API Manager.
>> Extremely sorry.
>>
>
> Yup, I missed the tag name and only noticed the label.
>
>>
>> Regards,
>>
>>
>>> Thanks,
>>> NuwanD.
>>>
>>> On Wed, Oct 10, 2018 at 1:42 AM Vimukthi Perera 
>>> wrote:
>>>
 WSO2 Installation Experience team is pleased to announce the release of
 Ansible, AWS, Docker, Kubernetes, Puppet and Vagrant resources for WSO2
 products.
 Ansible

 Related artifacts:

-

WSO2 API Manager v2.6.0.1 -
https://github.com/wso2/ansible-apim/releases/tag/v2.6.0.1
-

WSO2 Identity Server v5.7.0 -
https://github.com/wso2/ansible-is/releases/tag/v5.7.0.1
-

WSO2 Stream Processor v4.3.0 -
https://github.com/wso2/ansible-sp/releases/tag/v4.3.0.1
-

WSO2 Enterprise Integrator v6.4.0 -
https://github.com/wso2/ansible-ei/releases/tag/v6.4.0.1


 Issues:

-

WSO2 API Manager - https://github.com/wso2/ansible-apim/issues
-

WSO2 Identity Server - https://github.com/wso2/ansible-is/issues
-

WSO2 Stream Processor - https://github.com/wso2/ansible-sp/issues
-

WSO2 Enterprise Integrator -
https://github.com/wso2/ansible-ei/issues

 AWS

 Related artifacts:

-

WSO2 API Manager v2.6.0.1 -
https://github.com/wso2/aws-apim/releases/tag/v2.6.0.1
-

WSO2 Identity Server v5.7.0 -
https://github.com/wso2/aws-is/releases/tag/v5.7.0.1
-

WSO2 Stream Processor v4.3.0 -
https://github.com/wso2/aws-sp/releases/tag/v4.3.0.1
-

WSO2 Enterprise Integrator v6.4.0 -
https://github.com/wso2/aws-ei/releases/tag/v6.4.0.1


 Issues:

-

WSO2 API Manager - https://github.com/wso2/aws-apim/issues
-

WSO2 Identity Server - https://github.com/wso2/aws-is/issues
-

WSO2 Stream Processor - https://github.com/wso2/aws-sp/issues
-

WSO2 Enterprise Integrator - https://github.com/wso2/aws-ei/issues

 Docker

 Related artifacts:

-

WSO2 API Manager v2.6.0.1 -
https://github.com/wso2/docker-apim/releases/tag/v2.6.0.1
-

WSO2 Identity Server v5.7.0 -
https://github.com/wso2/docker-is/releases/tag/v5.7.0.1
-

WSO2 Stream Processor v4.3.0 -
https://github.com/wso2/docker-sp/releases/tag/v4.3.0.1
-

WSO2 Enterprise Integrator v6.4.0 -
https://github.com/wso2/docker-ei/releases/tag/v6.4.0.1


 Issues:

-

WSO2 API Manager - https://github.com/wso2/docker-apim/issues
-

WSO2 Identity Server - https://github.com/wso2/docker-is/issues
-

WSO2 Stream Processor - https://github.com/wso2/docker-sp/issues
-

WSO2 Enterprise Integrator -
https://github.com/wso2/docker-ei/issues

 Kubernetes

 Related artifacts:

-

WSO2 API Manager v2.6.0.1 -
https://github.com/wso2/kubernetes-apim/releases/tag/v2.6.0.1
-

WSO2 Identity Server v5.7.0 -
https://github.com/wso2/kubernetes-is/releases/tag/v5.7.0.1
-

WSO2 Stream Processor v4.3.0 -
https://github.com/wso2/kubernetes-sp/releases/tag/v4.3.0.1
-

WSO2 Enterprise Integrator v6.4.0 -
https://github.com/wso2/kubernetes-ei/releases/tag/v6.4.0.1


 Issues:

-

WSO2 API Manager - https://github.com/wso2/kubernetes-apim/issues
-

WSO2 Identity Server - https://github.com/wso2/kubernetes-is/issues
-

WSO2 Stream Processor - https://github.com/wso2/kubernetes-sp/issues
-

WSO2 Enterprise Integrator -
https://github.com/wso2/kubernetes-ei/issues

 Puppet

 Related 

[Dev] [Announce] [Architecture] WSO2 Stream Processor 4.3.0 Released!

[Dilini Muthumala]

WSO2 Stream Processor 4.3.0 Released!

WSO2 Stream Processor team is pleased to announce the release of version
4.3.0 of the WSO2 Stream Processor.

WSO2 Stream Processor is an open source embodiment of the WSO2 Analytics
platform, of which the real-time, incremental & intelligent data processing
capabilities let digital businesses create actionable business insights and
data products.

You can download this distribution from
https://wso2.com/analytics-and-stream-processing/install/

Online documentation is available at
https://docs.wso2.com/display/SP430/Stream+Processor+Documentation.
How to Run

1. Extract the downloaded zip.


2. Navigate to the /bin directory ( is the extracted
directory).


3. Issue one of the following commands to start the preferred runtime as
below,


For WSO2 Stream Processor Studio,

   -

   For Windows: editor.bat
   -

   For Linux: ./editor.sh


*For WSO2 Stream Processor Worker Runtime,*



* - For Windows: worker.bat- For Linux: ./worker.shFor WSO2 Stream
Processor Manager Runtime,*



* - For Windows: manager.bat- For Linux: ./manager.sh*
*For WSO2 Stream Processor Dashboard Runtime,*


* - For Windows: dashboard.bat- For Linux: ./dashboard.sh*

By default, the OSGi console starts with the server.
New Features in this Release

   - Improved architecture for High Availability (HA) deployment.
   - Distinct Count for Siddhi incremental aggregations.
   - Handling out of order events in incremental aggregations.
   - HTTP Request Sink and HTTP Response Source.
   - Support file downloads in HTTP Request Sink and HTTP Response Source.
   - Support attachments in Siddhi Email extension.
   - RDBMS CUD extension for performing SQL CUD (INSERT, UPDATE, DELETE)
   operations in Siddhi queries.
   - Siddhi extension for retrieving the city or country based on the given
   IP address.
   - Siddhi extension for filling string templates.
   - Siddhi extension to retrieve data from JSONs and inserting/modifying
   elements in JSONs using Siddhi streams.
   - Purging capability for incremental aggregation tables.
   - Siddhi extension to find the public origin IP from the given
   X-Forwarded header.
   - Open tracing client for Stream Processor.
   - Siddhi event table for Elasticsearch.
   - Report generation for dashboards and widgets
   - Siddhi extension to receive and publish events from/to IBM MQ.
   - Contains check for Siddhi RDBMS store.
   - Support to export the dashboard and its widgets as PDF files.
   - Enterprise Integrator analytics solution.
   - API Manager analytics solution.
   - Identity Server analytics solution.

Please find the GitHub issues related to these improvements and fixes here

Known Issues

All the open issues pertaining to WSO2 Stream Processor are reported at the
following location:

Stream Processor Issues

How You Can ContributeMailing Lists

Join our mailing list and correspond with the developers directly.

Developer list : dev@wso2.org | Subscribe | Mail Archive


User forum : StackOverflow

Reporting Issues

We encourage you to report issues, documentation faults, and feature
requests regarding WSO2 *Stream Processor* through the public Stream
Processor Git Repo .
Support

We are committed to ensure your enterprise middleware deployment is
completely supported from evaluation to production. Our unique approach
ensures that all support leverages our open development methodology and is
provided by the very same engineers who build the technology. For more
details and to take advantage of this unique opportunity, visit
http://wso2.com/support/


For more information about WSO2 Stream Processor, please see
https://wso2.com/analytics-and-stream-processing/ or visit the WSO2 Oxygen
Tank developer portal for additional resources.


Thank you for your interest in WSO2 Stream Processor.


-The WSO2 Stream Processor Team-
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev