Hello; We have upgraded the Android Dashboard App to the 16.04 version and modified the AuthenticationListener callbacks.
After that we have successfully run the onboarding and config services via Dashboard App. (Android Dashboard AJSCL 16.04 with AJTCL 16.04) If anyone needs, we can share and/or contribute the modified version of the app. Best. On Fri, Sep 9, 2016 at 9:13 PM, Lioy, Marcello <[email protected]> wrote: > Indeed thanks for sharing your experiences. Helpful to the community! > > > > *From:* [email protected] [mailto:[email protected]] *On Behalf Of > *Fatih > Aksel > *Sent:* Friday, September 09, 2016 7:59 AM > *To:* Peter Nisbet <[email protected]> > *Cc:* Lioy, Marcello <[email protected]>; allseen-core@lists. > allseenalliance.org; [email protected] > *Subject:* Re: [Allseen-baseservices] Issues accessing config and > onboarding services after upgrading to 16.04a > > > > We are using standard Dashboard App (https://git.allseenalliance. > org/cgit/contributed_applications/dashboard.git/) and we have been > modifiying it. > > > > We also tried the Onboarding Sample Client App ( > https://allseenalliance.org/framework/documentation/ > develop/run-sample-apps/onboarding/android) and experienced the same > problem. I also attached the some part of the log file. > > > > Thin client version was 15.09 and now we are also upgrading it to the > 16.04. > > > > Let you know if we will get any progress. > > > > Best, > > > > > > > > W/System.err( 4595): org.alljoyn.bus.BusException: ER_AUTH_FAIL > > W/System.err( 4595): at > org.alljoyn.bus.ProxyBusObject.getProperty(Native > Method) > > W/System.err( 4595): at org.alljoyn.bus.ProxyBusObject.access$400( > ProxyBusObject.java:35) > > W/System.err( 4595): at org.alljoyn.bus. > ProxyBusObject$Handler.invoke(ProxyBusObject.java:274) > > W/System.err( 4595): at java.lang.reflect.Proxy. > invoke(Proxy.java:397) > > W/System.err( 4595): at $Proxy3.getLastError(Unknown Source) > > W/System.err( 4595): at org.alljoyn.onboarding.client. > OnboardingClientImpl.GetLastError(OnboardingClientImpl.java:151) > > W/System.err( 4595): at org.alljoyn.onboarding.test. > OnboardingApplication.getLastError(OnboardingApplication.java:459) > > W/System.err( 4595): at org.alljoyn.onboarding.test. > OnboardingActivity$7.doInBackground(OnboardingActivity.java:304) > > W/System.err( 4595): at org.alljoyn.onboarding.test. > OnboardingActivity$7.doInBackground(OnboardingActivity.java:1) > > > > > > On Fri, Sep 9, 2016 at 5:45 PM, Peter Nisbet <[email protected]> > wrote: > > Thanks Fatih for sharing your experiences with the 16.04 thin client. Out > of curiosity do you have a custom Alljoyn app aside from the dashboard app? > If you do does it also have issues accessing the onboarding and config > services? Also what version of thin client were you using before you > updated to 16.04? > > > > Regards, > > > > Peter > > > > > > On Fri, Sep 9, 2016 at 10:19 AM, Fatih Aksel <[email protected]> wrote: > > Hello Peter, > > > > I would like to note that we are also experiencing the same accessing > issues with Onboarding and Config Services. We also believe that it is a > security issue since Thin Client services (onboarding and config) are > registered but we can't issue a method call through Dashboard App. > > > > Currently, we have upgraded the Dashboard App's AllJoyn libraries (jars > and so file) to the 16.04 and trying to understand the inner structure of > the app and update it is security mechanism. > > > > We'll update and report if there will be any progress. > > > > Best > > > > > > On Fri, Sep 2, 2016 at 11:25 PM, Lioy, Marcello <[email protected]> > wrote: > > Thanks Peter. If you find issues you can file a bug in the Core Jira – > the more information on the issue the better: > https://jira.allseenalliance.org/projects/ASACORE > > > > *From:* Peter Nisbet [mailto:[email protected]] > *Sent:* Friday, September 02, 2016 1:14 PM > *To:* Lioy, Marcello <[email protected]> > *Cc:* [email protected]; allseen-core@lists. > allseenalliance.org > *Subject:* Re: Issues accessing config and onboarding services after > upgrading to 16.04a > > > > Thanks for the information Marcello, I'll give it a try and report back if > there are issues. > > > > Cheers, > > > > Peter > > On Friday, 2 September 2016, Lioy, Marcello <[email protected]> > wrote: > > 15.09 iOS support was not official on of the reasons for this is that > support for Security 2.0 was not exposed of iOS (or Java for that matter). > I would recommend that you try with the 16.04a iOS binding as that was > officially supported, and if you see issues there with security the Core WG > will have to seriously consider fixing it as that might imply an > interoperability issue. > > > > *From:* Peter Nisbet [mailto:[email protected]] > *Sent:* Friday, September 02, 2016 11:45 AM > *To:* Lioy, Marcello <[email protected]> > *Cc:* [email protected]; allseen-core@lists. > allseenalliance.org > *Subject:* Re: [Allseen-core] Issues accessing config and onboarding > services after upgrading to 16.04a > > > > Hello Marcello, > > > > Thank you for providing some information regarding our issue accessing the > Onboarding and configuration services after our upgrade. It explains why > our 14.12 version of our app didn't work, however we do have a 15.09 > version of our Alljoyn mobile app running on IOS which is also unable to > access these services. > > > > I would assume that as the 15.09 app is able to complete the handshake > process but is unable to access the onboarding or configuration services is > due to a permission issue, is this related to not having a policy installed > on our device running 16.04 thin client? If this is the case how is a > policy obtained for the thin client device? > > > > Thank you for any further information you can provide on this issue, > > > > Cheers, > > > > Peter > > > Peter Nisbet, MASc, C.E.T > > Electronics Engineer > > > > Heaven Fresh Canada Inc. > > 1600 Aimco Blvd., Unit 5 > > Mississauga ON L4W 1V1 > > Cell: +1.647.377.2489 > > http://www.heavenfresh.ca > > > > Linkedin <http://ca.linkedin.com/in/peternisbet265> > > > > On Fri, Sep 2, 2016 at 2:08 PM, Lioy, Marcello <[email protected]> > wrote: > > You are correct there are changes in security that are not compatible > between 14.12 and 16.04. The issue is likely with the Dashboard > application, which was open sourced (https://git.allseenalliance. > org/cgit/contributed_applications/dashboard.git/) a while back. > Depending on your product requirements you may wish to updated the > dashboard project to use the new security features. Unfortunately no one > is currently maintaining that project, but was made available exactly for > situations like these. If you do so it would be great if you upstreamed > your changes! > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Peter > Nisbet > *Sent:* Wednesday, August 31, 2016 12:41 PM > *To:* [email protected]; allseen-core@lists. > allseenalliance.org > *Subject:* [Allseen-core] Issues accessing config and onboarding services > after upgrading to 16.04a > > > > Hello All, > > > > I've recently been working on upgrading our smart home products from AJTCL > version 14.12 to 16.04a and I've ran into issues accessing the onboarding > and configuration services of the device. > > > > I can access our custom device control panel and control our > device through our Alljoyn app after the upgrade to 16.04. Our control > panel uses an unsecured interface, while I believe the configuration and > onboarding interfaces are secured. This leads me to believe that there is > some issue with the security settings for our products, as there appear to > be significant changes between the security of 14.12 and 16.04. > > > > If I bypass calls for authorisation, policy and ACL functions I am able to > load the config and onboarding services, however this only works with 15.09 > or above versions of Alljoyn, as the dashboard app running 14.12 asks > repeatedly for a passcode. > > > > In the logs I've collected from the device I noticed that the function > AJ_PolicyLoad(); in AJ_PeerHandleExchangeGUIDs returns with error no policy > found. Could this be causing issues as I'd assume not having a policy would > prevent access to interface methods for the secured interface. > > > > It appears the interface methods for the onboarding and config services > are being registered in the access control list as I see this being done as > the device starts up. > > > > In the device logs I notice that on first attempt to access the onboarding > or config services, the device and app seem to fail at > AJ_PeerHandleKeyExchange(); with failed authentication, however restarting > the app on the phone and reconnecting to the device results in > authentication being successful and ultimately resulting a successful > handshake. The app however will repeatedly ask for a passcode when it tries > to call an interface method. I also see an error on the thin client for > FindAccessControlMember: Access table not initialized. > > > > Some information on our platform: > > OS: MQX 4.1 RTOS > > Alljoyn core version: 16.04a > > Base service version: 16.04 > > > > IOS App versions: 15.09 > > Android App: Dashboard 14.12 > > Cipher used is ALLJOYN_ECDHE_PSK > > > > If the issue is with not having a policy for the device please direct me > to where I can generate one. If it is not related to the policy is it some > other security issue and is it something that needs to be changed on the > thin client or mobile app. > > > > Any insight or information would be most appreciated. > > > > Thanks in advance, > > > > Peter > > > > > Peter Nisbet, MASc, C.E.T > > Electronics Engineer > > > > Heaven Fresh Canada Inc. > > 1600 Aimco Blvd., Unit 5 > > Mississauga ON L4W 1V1 > > Cell: +1.647.377.2489 > > http://www.heavenfresh.ca > > > > Linkedin <http://ca.linkedin.com/in/peternisbet265> > > > > > > -- > > Peter Nisbet, MASc, C.E.T > > Electronics Engineer > > > > Heaven Fresh Canada Inc. > > 1600 Aimco Blvd., Unit 5 > > Mississauga ON L4W 1V1 > > Cell: +1.647.377.2489 > > http://www.heavenfresh.ca > > > > Linkedin <http://ca.linkedin.com/in/peternisbet265> > > > > > > _______________________________________________ > Allseen-baseservices mailing list > [email protected] > https://lists.allseenalliance.org/mailman/listinfo/allseen-baseservices > > > > > > -- > > Fatih AKSEL > > > > Onbiron Yazılım Bilişim Teknolojileri > > AR-GE Ltd. Şti. > > T: +90 312 284 96 19 > > M: +90 505 313 24 17 > > http://www.onbiron.com.tr/ > > > > > > > > -- > > Fatih AKSEL > > > > Onbiron Yazılım Bilişim Teknolojileri > > AR-GE Ltd. Şti. > > T: +90 312 284 96 19 > > M: +90 505 313 24 17 > > http://www.onbiron.com.tr/ > -- Fatih AKSEL Onbiron Yazılım Bilişim Teknolojileri AR-GE Ltd. Şti. T: +90 312 284 96 19 M: +90 505 313 24 17 http://www.onbiron.com.tr/
_______________________________________________ Allseen-core mailing list [email protected] https://lists.allseenalliance.org/mailman/listinfo/allseen-core
