[Dev] [Architecture] WSO2 IoT Server 3.0.0-BETA is Released

2016-12-24 Thread Rasika Perera 
WSO2 IoT Server 3.0.0 BETA

We are pleased to announce WSO2 IoT Server 3.0.0 BETA release. It can be
downloaded from https://github.com/wso2/product-iots/releases/
download/v3.0.0-BETA/wso2iot-3.0.0-BETA.zip

WSO2 IoT Server is an extensible, open-source, multi tenant, Internet of
Things Platform for implementing server-side of IoT Reference Architecture.
It comes with a few reference implementations for the device layer.
WSO2 IoT Server supports:

   - Device Management
  - Extensions for registering device types
  - Self-service enrollment and management of connected devices
  - Group, manage and monitor connected devices
  - Share device operations / data with other users
  - Distribution and management of applications and firmware to devices
  - Edge computing powered by WSO2 CEP streaming engine (Siddhi -
  https://github.com/wso2/siddhi )
  - OOTB support for some known device types such as Raspberry Pi,
  Arduino Uno, Android
   - IoT Protocol Support
  - Leverage MQTT, HTTP, Websockets and XMPP protocols for device
  communications with IoT Server Framework extension for adding more
  protocols and data formats
   - Analytics
  - Support for batch, interactive, real-time and predictive analytics
  through WSO2 DAS
   - Pre-built visualization support for sensor readings
  - View instant, visualized statistics of individual or multiple
  devices
  - Traverse through, analyse and zoom in/out of filtered data
  - Stats-API to write your own visualization
  - Pre-built graphs for common sensor reading types like temperature,
  velocity
   - API Management for App Development
  - Devices are represented as REST APIs
  - Develop applications using Device APIs
   - Identity and Access Management
  - Identity Management for devices
  - Token based access control for devices & operations (protect back
  end services via exposing device type APIs)
  - Support for SCEP protocol (encryption and authenticity)

Bug Fixes

   - [IOTS-137 ] - -Detup fails,
   logging exceptions
   - [IOTS-151 ] - Server startup
   fails when configured to use Oracle
   - [IOTS-160 ] - Although two
   roles are shown in roles section several roles are shown when assigning to
   users
   - [IOTS-172 ] - The db scripts
   are not executed with -Dsetup
   - [IOTS-176 ] - Creating a New
   Device Type - device-deployer build failed
   - [IOTS-177 ] - Device types fail
   to register to IOTS when configured with Oracle db
   - [IOTS-184 ] - Windows startup
   error on hadoop
   - [IOTS-195 ] - Single
   sign-on(SSO) cannot enable Between devicemgt and DS
   - [IOTS-201 ] - DashboardDeployer
   Gadget directory copying to Wrong path
   - [IOTS-239 ] - SSO failing due
   to getting the access token from APIM
   - [IOTS-316 ] - Publisher and
   store apps are not working
   - [IOTS-319 ] - Implement
   enrolment functionality for AndroidSens
   - [IOTS-325 ] - Unable to delete
   policies associated with a group
   - [IOTS-330 ] - Policy not added
   for Virtual firealarm
   - [IOTS-332 ] - Devices listing
   page doesn't honor analyticsEnabled and groupingEnabled configs
   - [IOTS-333 ] - Devices listing
   page doesn't honor analyticsEnabled and groupingEnabled configs
   - [IOTS-335 ] - View Dashboard
   Permissions missing in the role permission tree
   - [IOTS-337 ] - Permissions
   (except device-mgt permissions) added through carbon console gets removed
   when adding permissions through deviceMgt UI
   - [IOTS-340 ] - NPE for username
   thrown on Broker

Tasks Done

   - [IOTS-307 ] - Stabilize Android
   Sense + Integrating with new dashboard

Improvements

   - [IOTS-171 ] - Register User
   Form: username message
   - [IOTS-271 ] - Viewing Group
   Details
   - [IOTS-334 ] - Add three buttons
   to improve device enrollment screens
   - [IOTS-336 ] - The UI to
   download the Android Agent uses the old EMM UI
   - [IOTS-338 ] - Windows 1

Re: [Dev] [IoTS] what's the complete steps to change the admin password in IoTS alpha version

2016-12-24 Thread Ayyoob Hamza 
Hi Zhanwen,

The issue seems to be in the broker configuration. If you are using
IoTS-Alpha, there is a configuration issue which was fixed in the later
release[1]. The issue was username and password field for mqtt
configuration in broker.xml is been read as password and username
respectively.

[1] https://wso2.org/jira/browse/MB-1715

Thanks,
Ayyoob

*Ayyoob Hamza*
*Software Engineer*
WSO2 Inc.; http://wso2.com
email: ayy...@wso2.com cell: +94 77 1681010 <%2B94%2077%207779495>

On Fri, Dec 23, 2016 at 11:45 AM, 云展智创  wrote:

> Hi all,
>
> Could you tell me what’s the complete steps to change the admin password
> in IoTS alpha version? I had changed almost all the default admin password
> in configuration files but still got lots of following errors (for example,
> I change the password to smart):
>
> [2016-12-23 14:13:55,169]  WARN - CarbonAuthenticationUtil Failed
> Administrator login attempt 'smart[-1234]' at [2016-12-23 14:13:55,169+0800]
> [2016-12-23 14:13:55,169]  WARN - AuthenticationHandler Illegal access
> attempt at [2016-12-23 14:13:55,0169] from IP address 127.0.0.1 while
> trying to authenticate access to service OAuth2TokenValidationService
> [2016-12-23 14:13:55,170] ERROR - OAuth2BasedMQTTAuthenticator Error on
> connecting with the validation endpoint.
> org.apache.axis2.AxisFault: Access Denied. Authentication failed - Invalid
> credentials provided.
> at org.apache.axis2.util.Utils.getInboundFaultFromMessageCont
> ext(Utils.java:531)
> at org.apache.axis2.description.OutInAxisOperationClient.handleResponse(
> OutInAxisOperation.java:370)
> at org.apache.axis2.description.OutInAxisOperationClient.send(
> OutInAxisOperation.java:445)
> at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(
> OutInAxisOperation.java:225)
> at org.apache.axis2.client.OperationClient.execute(
> OperationClient.java:149)
> at org.wso2.carbon.identity.oauth2.stub.OAuth2TokenValidationServiceSt
> ub.validate(OAuth2TokenValidationServiceStub.java:461)
> at org.wso2.carbon.andes.authentication.andes.
> OAuth2BasedMQTTAuthenticator.getAuthenticationInfo(
> OAuth2BasedMQTTAuthenticator.java:126)
> at org.wso2.carbon.andes.authentication.andes.
> OAuth2BasedMQTTAuthenticator.validateToken(OAuth2BasedMQTTAuthenticator.
> java:82)
> at org.wso2.carbon.andes.authentication.andes.
> OAuth2BasedMQTTAuthenticator.checkValid(OAuth2BasedMQTTAuthenticator.
> java:62)
> at org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor.
> processConnect(ProtocolProcessor.java:256)
> at org.dna.mqtt.moquette.messaging.spi.impl.SimpleMessaging.onEvent(
> SimpleMessaging.java:160)
> at org.dna.mqtt.moquette.messaging.spi.impl.SimpleMessaging.onEvent(
> SimpleMessaging.java:47)
> at com.lmax.disruptor.BatchEventProcessor.run(
> BatchEventProcessor.java:128)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(
> ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(
> ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> [2016-12-23 14:13:55,170]  INFO - ProtocolProcessor Lost connection with
> client paho6643675267853545
> [2016-12-23 14:13:55,171]  WARN - ProtocolProcessor
> MQTTAuthorizationSubject for client ID paho6643675267853545 is not removed
> since the entry does not exist
> [2016-12-23 14:13:55,171]  INFO - ProtocolProcessor Lost connection with
> client paho6643673511277781
> [2016-12-23 14:13:55,171]  WARN - ProtocolProcessor
> MQTTAuthorizationSubject for client ID paho6643673511277781 is not removed
> since the entry does not exist
> [2016-12-23 14:13:55,172]  INFO - ProtocolProcessor Lost connection with
> client paho6643673893486011
> [2016-12-23 14:13:55,172]  WARN - ProtocolProcessor
> MQTTAuthorizationSubject for client ID paho6643673893486011 is not removed
> since the entry does not exist
> [2016-12-23 14:13:55,172] ERROR - MQTTAdapterListener MQTT Exception
> occurred when starting listener
> Bad user name or password (4)
> at org.eclipse.paho.client.mqttv3.internal.ExceptionHelper.
> createMqttException(ExceptionHelper.java:28)
> at org.eclipse.paho.client.mqttv3.internal.ClientState.
> notifyReceivedAck(ClientState.java:885)
> at org.eclipse.paho.client.mqttv3.internal.CommsReceiver.
> run(CommsReceiver.java:118)
> at java.lang.Thread.run(Thread.java:745)
>
>
>
>
> Thanks!
>
> －－
> Zhanwen Zhou (Jason),
> +86 13922218435 <+86%20139%202221%208435>
> zhanwen.z...@smartcloudex.com
> Guangzhou Smart Cloudex Technology Co., Ltd.
> Business: IOT, API
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Password Policy by tenant

2016-12-24 Thread Kasun Bandara 
Hi Koné,

You can find the corresponding 'identity governance' features [Tenant wise
Password/Login/Account Management Policies] you have stated under
*'Identity-provider'->'Resident
Identity provider' *in the IS 5.3.0 Beta pack. In the final release (IS
5.3.0) this will be given as '*Resident*' under Main page.

Regards,
Kasun.




Kasun Gayan Bandara
PhD Research Student
Machine Learning Group

Faculty of Information Technology, Clayton
Monash University
25 Exhibition Walk, Clayton Campus
Wellington Road
Clayton VIC 3800
Australia.

E: herath.band...@monash.edu
M (+61) 43 491 6476





On Fri, Dec 23, 2016 at 9:08 PM, Koné Alioune Badara <
kon...@etna-alternance.net> wrote:

> Hello,
>
> In the Wso2 IS 5.3.0-Alpha you introduced a new tab in the left menu
> called 'governance' in which we can choose a password policy by tenant, but
> this tab is not there anymore in the 5.3.0-beta. We'll it be in the final
> official release?
>
> Also, in the 5.2.0, when you only give the login right to a user, it can
> changes his password, but no more in the 5.3.0-beta, is this behaviour will
> change from the 5.2.0 to the 5.3.0 ?
>
> Regards,
>
> Alioune B KONÉ.
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev